Group Common DCI for Wireless Resources

ABSTRACT

Systems, apparatuses, and methods are described for wireless communications. A base station may send, to a wireless device, one or more radio resource control messages comprising parameters for one or more bandwidth parts or other wireless resources. The base station may send, to the wireless device, downlink control information comprising one or more bandwidth part identifiers. The wireless device may switch, based on the downlink control information, from a first bandwidth part to a second bandwidth part.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of and claims priority to U.S. patentapplication Ser. No. 16/171,800, filed Oct. 26, 2018, which claims thebenefit of U.S. Provisional Application No. 62/577,995, filed on Oct.27, 2017, each of which is hereby incorporated by reference in itsentirety.

BACKGROUND

In wireless communications, bandwidth parts and other wireless resourcesmay be used by wireless devices. A base station may determine that oneor more wireless devices should use or switch to one or more bandwidthparts or other wireless resources. It is desired to improve wirelesscommunications without adversely increasing signaling overhead and/ordecreasing spectral efficiency.

SUMMARY

The following summary presents a simplified summary of certain features.The summary is not an extensive overview and is not intended to identifykey or critical elements.

Systems, apparatuses, and methods are described for communicationsassociated with switching bandwidth parts or other wireless resources. Abase station may send, to a wireless device, one or more radio resourcecontrol messages comprising parameters for one or more bandwidth partsand/or an index or an identifier associated with the wireless device.The base station may send, to the wireless device, downlink controlinformation comprising one or more bandwidth part identifiers. Thewireless device may determine, based on the index or the identifier forthe wireless device, a position of a bandwidth part identifier in thedownlink control information. The wireless device may switch from afirst bandwidth part to a second bandwidth part indicated by thebandwidth part identifier.

These and other features and advantages are described in greater detailbelow.

BRIEF DESCRIPTION OF THE DRAWINGS

Some features are shown by way of example, and not by limitation, in theaccompanying drawings. In the drawings, like numerals reference similarelements.

FIG. 1 shows example sets of orthogonal frequency division multiplexing(OFDM) subcarriers.

FIG. 2 shows example transmission time and reception time for twocarriers in a carrier group.

FIG. 3 shows example OFDM radio resources.

FIG. 4 shows hardware elements of a base station and a wireless device.

FIG. 5A, FIG. 5B, FIG. 5C and FIG. 5D show examples for uplink anddownlink signal transmission.

FIG. 6 shows an example protocol structure with multi-connectivity.

FIG. 7 shows an example protocol structure with carrier aggregation (CA)and dual connectivity (DC).

FIG. 8 shows example timing advance group (TAG) configurations.

FIG. 9 shows example message flow in a random access process in asecondary TAG.

FIG. 10A and FIG. 10B show examples for interfaces between a 5G corenetwork and base stations.

FIG. 11A, FIG. 11B, FIG. 11C, FIG. 11D, FIG. 11E, and FIG. 11F showexamples for architectures of tight interworking between a 5G RAN and along term evolution (LTE) radio access network (RAN).

FIG. 12A, FIG. 12B, and FIG. 12C show examples for radio protocolstructures of tight interworking bearers.

FIG. 13A and FIG. 13B show examples for gNodeB (gNB) deployment.

FIG. 14 shows functional split option examples of a centralized gNBdeployment.

FIG. 15 shows an example of an index-based group common downlink controlinformation (DCI).

FIG. 16 shows an example of a group common DCI comprising one or more ofa plurality of bandwidth part identifiers.

FIG. 17 shows an example of a group common DCI comprising a bandwidthpart identifier and one or more wireless device identifiers.

FIG. 18 shows an example of a group common DCI comprising one or morebandwidth part fields.

FIG. 19 shows an example for a group common control message.

FIG. 20 shows an example of a group common control procedure forbandwidth part switching that may be performed by a base station.

FIG. 21 shows an example of a group common control procedure forbandwidth part switching that may be performed by a wireless device.

FIG. 22 shows example elements of a computing device that may be used toimplement any of the various devices described herein.

DETAILED DESCRIPTION

The accompanying drawings, which form a part hereof, show examples ofthe disclosure. It is to be understood that the examples shown in thedrawings and/or discussed herein are non-exclusive and that there areother examples of how the disclosure may be practiced.

Examples may enable operation of carrier aggregation and may be used inthe technical field of multicarrier communication systems. Examples mayrelate to bandwidth part switching in multicarrier communicationsystems.

The following acronyms are used throughout the present disclosure,provided below for convenience although other acronyms may be introducedin the detailed description:

-   -   3GPP 3rd Generation Partnership Project    -   5G 5th generation wireless systems    -   5GC 5G Core Network    -   ACK Acknowledgement    -   AMF Access and Mobility Management Function    -   ASIC application-specific integrated circuit    -   BPSK binary phase shift keying    -   CA carrier aggregation    -   CC component carrier    -   CDMA code division multiple access    -   CP cyclic prefix    -   CPLD complex programmable logic devices    -   CSI channel state information    -   CSS common search space    -   CU central unit    -   DC dual connectivity    -   DCI downlink control information    -   DFTS-OFDM discrete Fourier transform spreading OFDM    -   DL downlink    -   DU distributed unit    -   eLTE enhanced LTE    -   eMBB enhanced mobile broadband    -   eNB evolved Node B    -   EPC evolved packet core    -   E-UTRAN evolved-universal terrestrial radio access network    -   FDD frequency division multiplexing    -   FPGA field programmable gate arrays    -   Fs-C Fs-control plane    -   Fs-U Fs-user plane    -   gNB next generation node B    -   HARQ hybrid automatic repeat request    -   HDL hardware description languages    -   ID identifier    -   IE information element    -   LTE long term evolution    -   MAC media access control    -   MCG master cell group    -   MeNB master evolved node B    -   MIB master information block    -   MME mobility management entity    -   mMTC massive machine type communications    -   NACK Negative Acknowledgement    -   NAS non-access stratum    -   NG CP next generation control plane core    -   NGC next generation core    -   NG-C NG-control plane    -   NG-U NG-user plane    -   NR MAC new radio MAC    -   NR PDCP new radio PDCP    -   NR PHY new radio physical    -   NR RLC new radio RLC    -   NR RRC new radio RRC    -   NR new radio    -   NSSAI network slice selection assistance information    -   OFDM orthogonal frequency division multiplexing    -   PCC primary component carrier    -   PCell primary cell    -   PDCCH physical downlink control channel    -   PDCP packet data convergence protocol    -   PDU packet data unit    -   PHICH physical HARQ indicator channel    -   PHY physical    -   PLMN public land mobile network    -   PSCell primary secondary cell    -   pTAG primary timing advance group    -   PUCCH physical uplink control channel    -   PUSCH physical uplink shared channel    -   QAM quadrature amplitude modulation    -   QPSK quadrature phase shift keying    -   RA random access    -   RACH random access channel    -   RAN radio access network    -   RAP random access preamble    -   RAR random access response    -   RB resource blocks    -   RBG resource block groups    -   RLC radio link control    -   RRC radio resource control    -   RRM radio resource management    -   RV redundancy version    -   SCC secondary component carrier    -   SCell secondary cell    -   SCG secondary cell group    -   SC-OFDM single carrier-OFDM    -   SDU service data unit    -   SeNB secondary evolved node B    -   SFN system frame number    -   S-GW serving gateway    -   SIB system information block    -   SC-OFDM single carrier orthogonal frequency division        multiplexing    -   SRB signaling radio bearer    -   sTAG(s) secondary timing advance group(s)    -   TA timing advance    -   TAG timing advance group    -   TAI tracking area identifier    -   TAT time alignment timer    -   TDD time division duplexing    -   TDMA time division multiple access    -   TTI transmission time interval    -   TB transport block    -   UE user equipment    -   UL uplink    -   UPGW user plane gateway    -   URLLC ultra-reliable low-latency communications    -   VHDL VHSIC hardware description language    -   Xn-C Xn-control plane    -   Xn-U Xn-user plane    -   Xx-C Xx-control plane    -   Xx-U Xx-user plane

Examples may be implemented using various physical layer modulation andtransmission mechanisms. Example transmission mechanisms may include,but are not limited to: CDMA, OFDM, TDMA, Wavelet technologies, and/orthe like. Hybrid transmission mechanisms such as TDMA/CDMA, andOFDM/CDMA may also be employed. Various modulation schemes may be usedfor signal transmission in the physical layer. Examples of modulationschemes include, but are not limited to: phase, amplitude, code, acombination of these, and/or the like. An example radio transmissionmethod may implement QAM using BPSK, QPSK, 16-QAM, 64-QAM, 256-QAM,and/or the like. Physical radio transmission may be enhanced bydynamically or semi-dynamically changing the modulation and codingscheme depending on transmission requirements and radio conditions.

FIG. 1 shows example sets of OFDM subcarriers. As shown in this example,arrow(s) in the diagram may depict a subcarrier in a multicarrier OFDMsystem. The OFDM system may use technology such as OFDM technology,DFTS-OFDM, SC-OFDM technology, or the like. For example, arrow 101 showsa subcarrier transmitting information symbols. FIG. 1 is shown as anexample, and a typical multicarrier OFDM system may include moresubcarriers in a carrier. For example, the number of subcarriers in acarrier may be in the range of 10 to 10,000 subcarriers. FIG. 1 showstwo guard bands 106 and 107 in a transmission band. As shown in FIG. 1 ,guard band 106 is between subcarriers 103 and subcarriers 104. Theexample set of subcarriers A 102 includes subcarriers 103 andsubcarriers 104. FIG. 1 also shows an example set of subcarriers B 105.As shown, there is no guard band between any two subcarriers in theexample set of subcarriers B 105. Carriers in a multicarrier OFDMcommunication system may be contiguous carriers, non-contiguouscarriers, or a combination of both contiguous and non-contiguouscarriers.

FIG. 2 shows an example timing arrangement with transmission time andreception time for two carriers. A multicarrier OFDM communicationsystem may include one or more carriers, for example, ranging from 1 to10 carriers. Carrier A 204 and carrier B 205 may have the same ordifferent timing structures. Although FIG. 2 shows two synchronizedcarriers, carrier A 204 and carrier B 205 may or may not be synchronizedwith each other. Different radio frame structures may be supported forFDD and TDD duplex mechanisms. FIG. 2 shows an example FDD frame timing.Downlink and uplink transmissions may be organized into radio frames201. In this example, radio frame duration is 10 milliseconds (msec).Other frame durations, for example, in the range of 1 to 100 msec mayalso be supported. In this example, each 10 msec radio frame 201 may bedivided into ten equally sized subframes 202. Other subframe durationssuch as including 0.5 msec, 1 msec, 2 msec, and 5 msec may also besupported. Subframe(s) may consist of two or more slots (e.g., slots 206and 207). For the example of FDD, 10 subframes may be available fordownlink transmission and 10 subframes may be available for uplinktransmissions in each 10 msec interval. Uplink and downlinktransmissions may be separated in the frequency domain. A slot may be 7or 14 OFDM symbols for the same subcarrier spacing of up to 60 kHz withnormal CP. A slot may be 14 OFDM symbols for the same subcarrier spacinghigher than 60 kHz with normal CP. A slot may include all downlink, alluplink, or a downlink part and an uplink part, and/or alike. Slotaggregation may be supported, for example, data transmission may bescheduled to span one or multiple slots. For example, a mini-slot maystart at an OFDM symbol in a subframe. A mini-slot may have a durationof one or more OFDM symbols. Slot(s) may include a plurality of OFDMsymbols 203. The number of OFDM symbols 203 in a slot 206 may depend onthe cyclic prefix length and subcarrier spacing.

FIG. 3 shows an example of OFDM radio resources. The resource gridstructure in time 304 and frequency 305 is shown in FIG. 3 . Thequantity of downlink subcarriers or RBs may depend, at least in part, onthe downlink transmission bandwidth 306 configured in the cell. Thesmallest radio resource unit may be called a resource element (e.g.,301). Resource elements may be grouped into resource blocks (e.g., 302).Resource blocks may be grouped into larger radio resources calledResource Block Groups (RBG) (e.g., 303). The transmitted signal in slot206 may be described by one or several resource grids of a plurality ofsubcarriers and a plurality of OFDM symbols. Resource blocks may be usedto describe the mapping of certain physical channels to resourceelements. Other pre-defined groupings of physical resource elements maybe implemented in the system depending on the radio technology. Forexample, 24 subcarriers may be grouped as a radio block for a durationof 5 msec. A resource block may correspond to one slot in the timedomain and 180 kHz in the frequency domain (for 15 kHz subcarrierbandwidth and 12 subcarriers).

Multiple numerologies may be supported. A numerology may be derived byscaling a basic subcarrier spacing by an integer N. Scalable numerologymay allow at least from 15 kHz to 480 kHz subcarrier spacing. Thenumerology with 15 kHz and scaled numerology with different subcarrierspacing with the same CP overhead may align at a symbol boundary every 1msec in a NR carrier.

FIG. 4 shows hardware elements of a base station 401 and a wirelessdevice 406. A communication network 400 may include at least one basestation 401 and at least one wireless device 406. The base station 401may include at least one communication interface 402, one or moreprocessors 403, and at least one set of program code instructions 405stored in non-transitory memory 404 and executable by the one or moreprocessors 403. The wireless device 406 may include at least onecommunication interface 407, one or more processors 408, and at leastone set of program code instructions 410 stored in non-transitory memory409 and executable by the one or more processors 408. A communicationinterface 402 in the base station 401 may be configured to engage incommunication with a communication interface 407 in the wireless device406, such as via a communication path that includes at least onewireless link 411. The wireless link 411 may be a bi-directional link.The communication interface 407 in the wireless device 406 may also beconfigured to engage in communication with the communication interface402 in the base station 401. The base station 401 and the wirelessdevice 406 may be configured to send and receive data over the wirelesslink 411 using multiple frequency carriers. Base stations, wirelessdevices, and other communication devices may include structure andoperations of transceiver(s). A transceiver is a device that includesboth a transmitter and receiver. Transceivers may be employed in devicessuch as wireless devices, base stations, relay nodes, and/or the like.Examples for radio technology implemented in the communicationinterfaces 402, 407 and the wireless link 411 are shown in FIG. 1 , FIG.2 , FIG. 3 , FIG. 5 , and associated text. The communication network 400may comprise any number and/or type of devices, such as, for example,computing devices, wireless devices, mobile devices, handsets, tablets,laptops, internet of things (IoT) devices, hotspots, cellular repeaters,computing devices, and/or, more generally, user equipment (e.g., UE).Although one or more of the above types of devices may be referencedherein (e.g., UE, wireless device, computing device, etc.), it should beunderstood that any device herein may comprise any one or more of theabove types of devices or similar devices. The communication network400, and any other network referenced herein, may comprise an LTEnetwork, a 5G network, or any other network for wireless communications.Apparatuses, systems, and/or methods described herein may generally bedescribed as implemented on one or more devices (e.g., wireless device,base station, eNB, gNB, computing device, etc.), in one or morenetworks, but it will be understood that one or more features and stepsmay be implemented on any device and/or in any network. As usedthroughout, the term “base station” may comprise one or more of: a basestation, a node, a Node B, a gNB, an eNB, an ng-eNB, a relay node (e.g.,an integrated access and backhaul (IAB) node), a donor node (e.g., adonor eNB, a donor gNB, etc.), an access point (e.g., a WiFi accesspoint), a computing device, a device capable of wirelesslycommunicating, or any other device capable of sending and/or receivingsignals. As used throughout, the term “wireless device” may comprise oneor more of: a UE, a handset, a mobile device, a computing device, anode, a device capable of wirelessly communicating, or any other devicecapable of sending and/or receiving signals. Any reference to one ormore of these terms/devices also considers use of any other term/devicementioned above.

The communications network 400 may comprise Radio Access Network (RAN)architecture. The RAN architecture may comprise one or more RAN nodesthat may be a next generation Node B (gNB) (e.g., 401) providing NewRadio (NR) user plane and control plane protocol terminations towards afirst wireless device (e.g. 406). A RAN node may be a next generationevolved Node B (ng-eNB), providing Evolved UMTS Terrestrial Radio Access(E-UTRA) user plane and control plane protocol terminations towards asecond wireless device. The first wireless device may communicate with agNB over a Uu interface. The second wireless device may communicate witha ng-eNB over a Uu interface. Base station 401 may comprise one or moreof a gNB, ng-eNB, and/or the like.

A gNB or an ng-eNB may host functions such as: radio resource managementand scheduling, IP header compression, encryption and integrityprotection of data, selection of Access and Mobility Management Function(AMF) at User Equipment (UE) attachment, routing of user plane andcontrol plane data, connection setup and release, scheduling andtransmission of paging messages (originated from the AMF), schedulingand transmission of system broadcast information (originated from theAMF or Operation and Maintenance (O&M)), measurement and measurementreporting configuration, transport level packet marking in the uplink,session management, support of network slicing, Quality of Service (QoS)flow management and mapping to data radio bearers, support of wirelessdevices in RRC_INACTIVE state, distribution function for Non-AccessStratum (NAS) messages, RAN sharing, and dual connectivity or tightinterworking between NR and E-UTRA.

One or more gNBs and/or one or more ng-eNBs may be interconnected witheach other by means of Xn interface. A gNB or an ng-eNB may be connectedby means of NG interfaces to 5G Core Network (5GC). 5GC may comprise oneor more AMF/User Plane Function (UPF) functions. A gNB or an ng-eNB maybe connected to a UPF by means of an NG-User plane (NG-U) interface. TheNG-U interface may provide delivery (e.g., non-guaranteed delivery) ofuser plane Protocol Data Units (PDUs) between a RAN node and the UPF. AgNB or an ng-eNB may be connected to an AMF by means of an NG-Controlplane (e.g., NG-C) interface. The NG-C interface may provide functionssuch as NG interface management, UE context management, UE mobilitymanagement, transport of NAS messages, paging, PDU session management,configuration transfer or warning message transmission.

A UPF may host functions such as anchor point for intra-/inter-RadioAccess Technology (RAT) mobility (if applicable), external PDU sessionpoint of interconnect to data network, packet routing and forwarding,packet inspection and user plane part of policy rule enforcement,traffic usage reporting, uplink classifier to support routing trafficflows to a data network, branching point to support multi-homed PDUsession, QoS handling for user plane, for example, packet filtering,gating, Uplink (UL)/Downlink (DL) rate enforcement, uplink trafficverification (e.g. Service Data Flow (SDF) to QoS flow mapping),downlink packet buffering and/or downlink data notification triggering.

An AMF may host functions such as NAS signaling termination, NASsignaling security, Access Stratum (AS) security control, inter CoreNetwork (CN) node signaling for mobility between 3^(rd) GenerationPartnership Project (3GPP) access networks, idle mode UE reachability(e.g., control and execution of paging retransmission), registrationarea management, support of intra-system and inter-system mobility,access authentication, access authorization including check of roamingrights, mobility management control (subscription and policies), supportof network slicing and/or Session Management Function (SMF) selection

An interface may be a hardware interface, a firmware interface, asoftware interface, and/or a combination thereof. The hardware interfacemay include connectors, wires, electronic devices such as drivers,amplifiers, and/or the like. A software interface may include codestored in a memory device to implement protocol(s), protocol layers,communication drivers, device drivers, combinations thereof, and/or thelike. A firmware interface may include a combination of embeddedhardware and code stored in and/or in communication with a memory deviceto implement connections, electronic device operations, protocol(s),protocol layers, communication drivers, device drivers, hardwareoperations, combinations thereof, and/or the like.

The term configured may relate to the capacity of a device whether thedevice is in an operational or a non-operational state. Configured mayalso refer to specific settings in a device that effect the operationalcharacteristics of the device whether the device is in an operational ora non-operational state. In other words, the hardware, software,firmware, registers, memory values, and/or the like may be “configured”within a device, whether the device is in an operational or anonoperational state, to provide the device with specificcharacteristics. Terms such as “a control message to cause in a device”may mean that a control message has parameters that may be used toconfigure specific characteristics in the device, whether the device isin an operational or a non-operational state.

A network may include a multitude of base stations, providing a userplane NR PDCP/NR RLC/NR MAC/NR PHY and control plane (e.g., NR RRC)protocol terminations towards the wireless device. The base station(s)may be interconnected with other base station(s) (e.g., employing an Xninterface). The base stations may also be connected employing, forexample, an NG interface to an NGC. FIG. 10A and FIG. 10B show examplesfor interfaces between a 5G core network (e.g., NGC) and base stations(e.g., gNB and eLTE eNB). For example, the base stations may beinterconnected to the NGC control plane (e.g., NG CP) employing the NG-Cinterface and to the NGC user plane (e.g., UPGW) employing the NG-Uinterface. The NG interface may support a many-to-many relation between5G core networks and base stations.

A base station may include many sectors, for example: 1, 2, 3, 4, or 6sectors. A base station may include many cells, for example, rangingfrom 1 to 50 cells or more. A cell may be categorized, for example, as aprimary cell or secondary cell. At RRC connectionestablishment/re-establishment/handover, one serving cell may providethe NAS (non-access stratum) mobility information (e.g., TAI), and atRRC connection re-establishment/handover, one serving cell may providethe security input. This cell may be referred to as the Primary Cell(PCell). In the downlink, the carrier corresponding to the PCell may bethe Downlink Primary Component Carrier (DL PCC); in the uplink, thecarrier corresponding to the PCell may be the Uplink Primary ComponentCarrier (UL PCC). Depending on wireless device capabilities, SecondaryCells (SCells) may be configured to form together with the PCell a setof serving cells. In the downlink, the carrier corresponding to an SCellmay be a Downlink Secondary Component Carrier (DL SCC); in the uplink,the carrier corresponding to an SCell may be an Uplink SecondaryComponent Carrier (UL SCC). An SCell may or may not have an uplinkcarrier.

A cell, comprising a downlink carrier and optionally an uplink carrier,may be assigned a physical cell ID and a cell index. A carrier (downlinkor uplink) may belong to only one cell. The cell ID or cell index mayalso identify the downlink carrier or uplink carrier of the cell(depending on the context in which it is used). The cell ID may beequally referred to a carrier ID, and cell index may be referred tocarrier index. In implementation, the physical cell ID or cell index maybe assigned to a cell. A cell ID may be determined using asynchronization signal transmitted on a downlink carrier. A cell indexmay be determined using RRC messages. For example, reference to a firstphysical cell ID for a first downlink carrier may indicate that thefirst physical cell ID is for a cell comprising the first downlinkcarrier. The same concept may apply to, for example, carrier activation.Reference to a first carrier that is activated may indicate that thecell comprising the first carrier is activated.

A device may be configured to operate as needed by freely combining anyof the examples. The disclosed mechanisms may be performed if certaincriteria are met, for example, in a wireless device, a base station, aradio environment, a network, a combination of the above, and/or thelike. Example criteria may be based, at least in part, on for example,traffic load, initial system set up, packet sizes, trafficcharacteristics, a combination of the above, and/or the like. One ormore criteria may be satisfied. It may be possible to implement examplesthat selectively implement disclosed protocols.

A base station may communicate with a variety of wireless devices.Wireless devices may support multiple technologies, and/or multiplereleases of the same technology. Wireless devices may have some specificcapability(ies) depending on its wireless device category and/orcapability(ies). A base station may comprise multiple sectors. Referenceto a base station communicating with a plurality of wireless devices mayindicate that a base station may communicate with a subset of the totalwireless devices in a coverage area. A plurality of wireless devices ofa given LTE or 5G release, with a given capability and in a given sectorof the base station, may be used. The plurality of wireless devices mayrefer to a selected plurality of wireless devices, and/or a subset oftotal wireless devices in a coverage area which perform according todisclosed methods, and/or the like. There may be a plurality of wirelessdevices in a coverage area that may not comply with the disclosedmethods, for example, because those wireless devices perform based onolder releases of LTE or 5G technology.

A base station may transmit (e.g., to a wireless device) one or moremessages (e.g. RRC messages) that may comprise a plurality ofconfiguration parameters for one or more cells. One or more cells maycomprise at least one primary cell and at least one secondary cell. AnRRC message may be broadcasted or unicasted to the wireless device.Configuration parameters may comprise common parameters and dedicatedparameters.

Services and/or functions of an RRC sublayer may comprise at least oneof: broadcast of system information related to AS and NAS; paginginitiated by 5GC and/or NG-RAN; establishment, maintenance, and/orrelease of an RRC connection between a wireless device and NG-RAN, whichmay comprise at least one of addition, modification and release ofcarrier aggregation; or addition, modification, and/or release of dualconnectivity in NR or between E-UTRA and NR. Services and/or functionsof an RRC sublayer may further comprise at least one of securityfunctions comprising key management; establishment, configuration,maintenance, and/or release of Signaling Radio Bearers (SRBs) and/orData Radio Bearers (DRBs); mobility functions which may comprise atleast one of a handover (e.g. intra NR mobility or inter-RAT mobility)and a context transfer; or a wireless device cell selection andreselection and control of cell selection and reselection. Servicesand/or functions of an RRC sublayer may further comprise at least one ofQoS management functions; a wireless device measurementconfiguration/reporting; detection of and/or recovery from radio linkfailure; or NAS message transfer to/from a core network entity (e.g.AMF, Mobility Management Entity (MME)) from/to the wireless device.

An RRC sublayer may support an RRC_Idle state, an RRC_Inactive stateand/or an RRC_Connected state for a wireless device. In an RRC_Idlestate, a wireless device may perform at least one of: Public Land MobileNetwork (PLMN) selection; receiving broadcasted system information; cellselection/re-selection; monitoring/receiving a paging for mobileterminated data initiated by 5GC; paging for mobile terminated data areamanaged by 5GC; or DRX for CN paging configured via NAS. In anRRC_Inactive state, a wireless device may perform at least one of:receiving broadcasted system information; cell selection/re-selection;monitoring/receiving a RAN/CN paging initiated by NG-RAN/5GC; RAN-basednotification area (RNA) managed by NG-RAN; or DRX for RAN/CN pagingconfigured by NG-RAN/NAS. In an RRC_Idle state of a wireless device, abase station (e.g. NG-RAN) may keep a 5GC-NG-RAN connection (bothC/U-planes) for the wireless device; and/or store a UE AS context forthe wireless device. In an RRC_Connected state of a wireless device, abase station (e.g. NG-RAN) may perform at least one of: establishment of5GC-NG-RAN connection (both C/U-planes) for the wireless device; storinga UE AS context for the wireless device; transmit/receive of unicastdata to/from the wireless device; or network-controlled mobility basedon measurement results received from the wireless device. In anRRC_Connected state of a wireless device, an NG-RAN may know a cell thatthe wireless device belongs to.

System information (SI) may be divided into minimum SI and other SI. Theminimum SI may be periodically broadcast. The minimum SI may comprisebasic information required for initial access and information foracquiring any other SI broadcast periodically or provisioned on-demand,i.e. scheduling information. The other SI may either be broadcast, or beprovisioned in a dedicated manner, either triggered by a network or uponrequest from a wireless device. A minimum SI may be transmitted via twodifferent downlink channels using different messages (e.g.MasterlnformationBlock and SystemInformationBlockType1). The other SImay be transmitted via SystemInformationBlockType2. For a wirelessdevice in an RRC_Connected state, dedicated RRC signaling may beemployed for the request and delivery of the other SI. For the wirelessdevice in the RRC_Idle state and/or the RRC_Inactive state, the requestmay trigger a random-access procedure.

A wireless device may send its radio access capability information whichmay be static. A base station may request what capabilities for awireless device to report based on band information. If allowed by anetwork, a temporary capability restriction request may be sent by thewireless device to signal the limited availability of some capabilities(e.g. due to hardware sharing, interference or overheating) to the basestation. The base station may confirm or reject the request. Thetemporary capability restriction may be transparent to 5GC (e.g., staticcapabilities may be stored in 5GC).

If CA is configured, a wireless device may have an RRC connection with anetwork. At RRC connection establishment/re-establishment/handoverprocedure, one serving cell may provide NAS mobility information, and atRRC connection re-establishment/handover, one serving cell may provide asecurity input. This cell may be referred to as the PCell. Depending onthe capabilities of the wireless device, SCells may be configured toform together with the PCell a set of serving cells. The configured setof serving cells for the wireless device may comprise one PCell and oneor more SCells.

The reconfiguration, addition and removal of SCells may be performed byRRC. At intra-NR handover, RRC may also add, remove, or reconfigureSCells for usage with the target PCell. If adding a new SCell, dedicatedRRC signaling may be employed to send all required system information ofthe SCell. In connected mode, wireless devices may not need to acquirebroadcasted system information directly from the SCells.

An RRC connection reconfiguration procedure may be used to modify an RRCconnection, (e.g. to establish, modify and/or release RBs, to performhandover, to setup, modify, and/or release measurements, to add, modify,and/or release SCells and cell groups). As part of the RRC connectionreconfiguration procedure, NAS dedicated information may be transferredfrom the network to the wireless device. TheRRCConnectionReconfiguration message may be a command to modify an RRCconnection. It may convey information for measurement configuration,mobility control, radio resource configuration (e.g. RBs, MAC mainconfiguration and physical channel configuration) comprising anyassociated dedicated NAS information and security configuration. If thereceived RRC Connection Reconfiguration message includes thesCellToReleaseList, the wireless device may perform an SCell release. Ifthe received RRC Connection Reconfiguration message includes thesCellToAddModList, the wireless device may perform SCell additions ormodification.

An RRC connection establishment (or reestablishment, resume) proceduremay be used to establish (or reestablish, resume) an RRC connection. AnRRC connection establishment procedure may comprise SRB1 establishment.The RRC connection establishment procedure may be used to transfer theinitial NAS dedicated information message from a wireless device toE-UTRAN. The RRCConnectionReestablishment message may be used tore-establish SRB1.

A measurement report procedure may be to transfer measurement resultsfrom a wireless device to NG-RAN. The wireless device may initiate ameasurement report procedure, for example, after successful securityactivation. A measurement report message may be employed to transmitmeasurement results.

FIG. 5A, FIG. 5B, FIG. 5C, and FIG. 5D show examples of architecture foruplink and downlink signal transmission. FIG. 5A shows an example for anuplink physical channel. The baseband signal representing the physicaluplink shared channel may be processed according to the followingprocesses, which may be performed by structures described below. Thesestructures and corresponding functions are shown as examples, however,it is anticipated that other structures and/or functions may beimplemented in various examples. The structures and correspondingfunctions may comprise, for example, one or more scrambling devices 501Aand 501B configured to perform scrambling of coded bits in each of thecodewords to be transmitted on a physical channel; one or moremodulation mappers 502A and 502B configured to perform modulation ofscrambled bits to generate complex-valued symbols; a layer mapper 503configured to perform mapping of the complex-valued modulation symbolsonto one or several transmission layers; one or more transform precoders504A and 504B to generate complex-valued symbols; a precoding device 505configured to perform precoding of the complex-valued symbols; one ormore resource element mappers 506A and 506B configured to performmapping of precoded complex-valued symbols to resource elements; one ormore signal generators 507A and 507B configured to perform thegeneration of a complex-valued time-domain DFTS-OFDM/SC-FDMA signal foreach antenna port; and/or the like.

FIG. 5B shows an example for performing modulation and up-conversion tothe carrier frequency of the complex-valued DFTS-OFDM/SC-FDMA basebandsignal, for example, for each antenna port and/or for the complex-valuedphysical random access channel (PRACH) baseband signal. For example, thebaseband signal, represented as s₁(t), may be split, by a signalsplitter 510, into real and imaginary components, Re{s₁(t)} andIm{s₁(t)}, respectively. The real component may be modulated by amodulator 511A, and the imaginary component may be modulated by amodulator 511B. The output signal of the modulator 511A and the outputsignal of the modulator 511B may be mixed by a mixer 512. The outputsignal of the mixer 512 may be input to a filtering device 513, andfiltering may be employed by the filtering device 513 prior totransmission.

FIG. 5C shows an example structure for downlink transmissions. Thebaseband signal representing a downlink physical channel may beprocessed by the following processes, which may be performed bystructures described below. These structures and corresponding functionsare shown as examples, however, it is anticipated that other structuresand/or functions may be implemented in various examples. The structuresand corresponding functions may comprise, for example, one or morescrambling devices 531A and 531B configured to perform scrambling ofcoded bits in each of the codewords to be transmitted on a physicalchannel; one or more modulation mappers 532A and 532B configured toperform modulation of scrambled bits to generate complex-valuedmodulation symbols; a layer mapper 533 configured to perform mapping ofthe complex-valued modulation symbols onto one or several transmissionlayers; a precoding device 534 configured to perform precoding of thecomplex-valued modulation symbols on each layer for transmission on theantenna ports; one or more resource element mappers 535A and 535Bconfigured to perform mapping of complex-valued modulation symbols foreach antenna port to resource elements; one or more OFDM signalgenerators 536A and 536B configured to perform the generation ofcomplex-valued time-domain OFDM signal for each antenna port; and/or thelike.

FIG. 5D shows an example structure for modulation and up-conversion tothe carrier frequency of the complex-valued OFDM baseband signal foreach antenna port. For example, the baseband signal, represented as s₁^((p))(t), may be split, by a signal splitter 520, into real andimaginary components, Re{s^((p))(t)} and Im{s₁ ^((p))(t)}, respectively.The real component may be modulated by a modulator 521A, and theimaginary component may be modulated by a modulator 521B. The outputsignal of the modulator 521A and the output signal of the modulator 521Bmay be mixed by a mixer 522. The output signal of the mixer 522 may beinput to a filtering device 523, and filtering may be employed by thefiltering device 523 prior to transmission.

FIG. 6 and FIG. 7 show examples for protocol structures with CA andmulti-connectivity. NR may support multi-connectivity operation, wherebya multiple receiver/transmitter (RX/TX) wireless device in RRC_CONNECTEDmay be configured to utilize radio resources provided by multipleschedulers located in multiple gNBs connected via a non-ideal or idealbackhaul over the Xn interface. gNBs involved in multi-connectivity fora certain wireless device may assume two different roles: a gNB mayeither act as a master gNB (e.g., 600) or as a secondary gNB (e.g., 610or 620). In multi-connectivity, a wireless device may be connected toone master gNB (e.g., 600) and one or more secondary gNBs (e.g., 610and/or 620). Any one or more of the Master gNB 600 and/or the secondarygNBs 610 and 620 may be a Next Generation (NG) NodeB. The master gNB 600may comprise protocol layers NR MAC 601, NR RLC 602 and 603, and NR PDCP604 and 605. The secondary gNB may comprise protocol layers NR MAC 611,NR RLC 612 and 613, and NR PDCP 614. The secondary gNB may compriseprotocol layers NR MAC 621, NR RLC 622 and 623, and NR PDCP 624. Themaster gNB 600 may communicate via an interface 606 and/or via aninterface 607, the secondary gNB 610 may communicate via an interface615, and the secondary gNB 620 may communicate via an interface 625. Themaster gNB 600 may also communicate with the secondary gNB 610 and thesecondary gNB 621 via interfaces 608 and 609, respectively, which mayinclude Xn interfaces. For example, the master gNB 600 may communicatevia the interface 608, at layer NR PDCP 605, and with the secondary gNB610 at layer NR RLC 612. The master gNB 600 may communicate via theinterface 609, at layer NR PDCP 605, and with the secondary gNB 620 atlayer NR RLC 622.

FIG. 7 shows an example structure for the UE side MAC entities, forexample, if a Master Cell Group (MCG) and a Secondary Cell Group (SCG)are configured. Media Broadcast Multicast Service (MBMS) reception maybe included but is not shown in this figure for simplicity.

In multi-connectivity, the radio protocol architecture that a particularbearer uses may depend on how the bearer is set up. As an example, threealternatives may exist, an MCG bearer, an SCG bearer, and a splitbearer, such as shown in FIG. 6 . NR RRC may be located in a master gNBand SRBs may be configured as a MCG bearer type and may use the radioresources of the master gNB. Multi-connectivity may have at least onebearer configured to use radio resources provided by the secondary gNB.Multi-connectivity may or may not be configured or implemented.

For multi-connectivity, the wireless device may be configured withmultiple NR MAC entities: e.g., one NR MAC entity for a master gNB, andother NR MAC entities for secondary gNBs. In multi-connectivity, theconfigured set of serving cells for a wireless device may comprise twosubsets: e.g., the Master Cell Group (MCG) including the serving cellsof the master gNB, and the Secondary Cell Groups (SCGs) including theserving cells of the secondary gNBs.

At least one cell in a SCG may have a configured UL component carrier(CC) and one of the UL CCs, for example, named PSCell (or PCell of SCG,or sometimes called PCell), may be configured with PUCCH resources. Ifthe SCG is configured, there may be at least one SCG bearer or one splitbearer. If a physical layer problem or a random access problem on aPSCell occurs or is detected, if the maximum number of NR RLCretransmissions has been reached associated with the SCG, or if anaccess problem on a PSCell during a SCG addition or a SCG change occursor is detected, then an RRC connection re-establishment procedure maynot be triggered, UL transmissions towards cells of the SCG may bestopped, a master gNB may be informed by the wireless device of a SCGfailure type, and for a split bearer the DL data transfer over themaster gNB may be maintained. The NR RLC Acknowledge Mode (AM) bearermay be configured for the split bearer. Like the PCell, a PSCell may notbe de-activated. The PSCell may be changed with an SCG change (e.g.,with a security key change and a RACH procedure). A direct bearer typemay change between a split bearer and an SCG bearer, or a simultaneousconfiguration of an SCG and a split bearer may or may not be supported.

A master gNB and secondary gNBs may interact for multi-connectivity. Themaster gNB may maintain the RRM measurement configuration of thewireless device, and the master gNB may, (e.g., based on receivedmeasurement reports, and/or based on traffic conditions and/or bearertypes), decide to ask a secondary gNB to provide additional resources(e.g., serving cells) for a wireless device. If a request from themaster gNB is received, a secondary gNB may create a container that mayresult in the configuration of additional serving cells for the wirelessdevice (or the secondary gNB decide that it has no resource available todo so). For wireless device capability coordination, the master gNB mayprovide some or all of the Active Set (AS) configuration and thewireless device capabilities to the secondary gNB. The master gNB andthe secondary gNB may exchange information about a wireless deviceconfiguration, such as by employing NR RRC containers (e.g., inter-nodemessages) carried in Xn messages. The secondary gNB may initiate areconfiguration of its existing serving cells (e.g., PUCCH towards thesecondary gNB). The secondary gNB may decide which cell is the PSCellwithin the SCG. The master gNB may or may not change the content of theNR RRC configuration provided by the secondary gNB. In an SCG additionand an SCG SCell addition, the master gNB may provide the latestmeasurement results for the SCG cell(s). Both a master gNB and asecondary gNBs may know the system frame number (SFN) and subframeoffset of each other by operations, administration, and maintenance(OAM) (e.g., for the purpose of discontinuous reception (DRX) alignmentand identification of a measurement gap). If adding a new SCG SCell,dedicated NR RRC signaling may be used for sending required systeminformation of the cell for CA, except, for example, for the SFNacquired from an MIB of the PSCell of an SCG.

FIG. 7 shows an example of dual-connectivity (DC) for two MAC entitiesat a wireless device side. A first MAC entity may comprise a lower layerof an MCG 700, an upper layer of an MCG 718, and one or moreintermediate layers of an MCG 719. The lower layer of the MCG 700 maycomprise, for example, a paging channel (PCH) 701, a broadcast channel(BCH) 702, a downlink shared channel (DL-SCH) 703, an uplink sharedchannel (UL-SCH) 704, and a random access channel (RACH) 705. The one ormore intermediate layers of the MCG 719 may comprise, for example, oneor more hybrid automatic repeat request (HARQ) processes 706, one ormore random access control processes 707, multiplexing and/orde-multiplexing processes 709, logical channel prioritization on theuplink processes 710, and a control processes 708 providing control forthe above processes in the one or more intermediate layers of the MCG719. The upper layer of the MCG 718 may comprise, for example, a pagingcontrol channel (PCCH) 711, a broadcast control channel (BCCH) 712, acommon control channel (CCCH) 713, a dedicated control channel (DCCH)714, a dedicated traffic channel (DTCH) 715, and a MAC control 716.

A second MAC entity may comprise a lower layer of an SCG 720, an upperlayer of an SCG 738, and one or more intermediate layers of an SCG 739.The lower layer of the SCG 720 may comprise, for example, a BCH 722, aDL-SCH 723, an UL-SCH 724, and a RACH 725. The one or more intermediatelayers of the SCG 739 may comprise, for example, one or more HARQprocesses 726, one or more random access control processes 727,multiplexing and/or de-multiplexing processes 729, logical channelprioritization on the uplink processes 730, and a control processes 728providing control for the above processes in the one or moreintermediate layers of the SCG 739. The upper layer of the SCG 738 maycomprise, for example, a BCCH 732, a DCCH 714, a DTCH 735, and a MACcontrol 736.

Serving cells may be grouped in a TA group (TAG). Serving cells in oneTAG may use the same timing reference. For a given TAG, a wirelessdevice may use at least one downlink carrier as a timing reference. Fora given TAG, a wireless device may synchronize uplink subframe and frametransmission timing of uplink carriers belonging to the same TAG.Serving cells having an uplink to which the same TA applies maycorrespond to serving cells hosted by the same receiver. A wirelessdevice supporting multiple TAs may support two or more TA groups. One TAgroup may include the PCell and may be called a primary TAG (pTAG). In amultiple TAG configuration, at least one TA group may not include thePCell and may be called a secondary TAG (sTAG). Carriers within the sameTA group may use the same TA value and/or the same timing reference. IfDC is configured, cells belonging to a cell group (e.g., MCG or SCG) maybe grouped into multiple TAGs including a pTAG and one or more sTAGs.

FIG. 8 shows example TAG configurations. In Example 1, a pTAG comprisesa PCell, and an sTAG comprises an SCell1. In Example 2, a pTAG comprisesa PCell and an SCell1, and an sTAG comprises an SCell2 and an SCell3. InExample 3, a pTAG comprises a PCell and an SCell1, and an sTAG1comprises an SCell2 and an SCell3, and an sTAG2 comprises a SCell4. Upto four TAGs may be supported in a cell group (MCG or SCG), and otherexample TAG configurations may also be provided. In various examples,structures and operations are described for use with a pTAG and an sTAG.Some of the examples may be used for configurations with multiple sTAGs.

An eNB may initiate an RA procedure, via a PDCCH order, for an activatedSCell. The PDCCH order may be sent on a scheduling cell of this SCell.If cross carrier scheduling is configured for a cell, the schedulingcell may be different than the cell that is employed for preambletransmission, and the PDCCH order may include an SCell index. At least anon-contention based RA procedure may be supported for SCell(s) assignedto sTAG(s).

FIG. 9 shows an example of random access processes, and a correspondingmessage flow, in a secondary TAG. A base station, such as an eNB, maytransmit an activation command 900 to a wireless device, such as a UE.The activation command 900 may be transmitted to activate an SCell. Thebase station may also transmit a PDDCH order 901 to the wireless device,which may be transmitted, for example, after the activation command 900.The wireless device may begin to perform a RACH process for the SCell,which may be initiated, for example, after receiving the PDDCH order901. A wireless device may transmit to the base station (e.g., as partof a RACH process) a preamble 902 (e.g., Msg1), such as a random accesspreamble (RAP). The preamble 902 may be transmitted after or in responseto the PDCCH order 901. The wireless device may transmit the preamble902 via an SCell belonging to an sTAG. Preamble transmission for SCellsmay be controlled by a network using PDCCH format 1A. The base stationmay send a random access response (RAR) 903 (e.g., Msg2 message) to thewireless device. The RAR 903 may be after or in response to the preamble902 transmission via the SCell. The RAR 903 may be addressed to a randomaccess radio network temporary identifier (RA-RNTI) in a PCell commonsearch space (CSS). If the wireless device receives the RAR 903, theRACH process may conclude. The RACH process may conclude, for example,after or in response to the wireless device receiving the RAR 903 fromthe base station. After the RACH process, the wireless device maytransmit an uplink transmission 904. The uplink transmission 904 maycomprise uplink packets transmitted via the same SCell used for thepreamble 902 transmission.

Timing alignment (e.g., initial timing alignment) for communicationsbetween the wireless device and the base station may be performedthrough a random access procedure, such as described above regardingFIG. 9 . The random access procedure may involve a wireless device, suchas a UE, transmitting a random access preamble and a base station, suchas an eNB, responding with an initial TA command NTA (amount of timingadvance) within a random access response window. The start of the randomaccess preamble may be aligned with the start of a corresponding uplinksubframe at the wireless device assuming NTA=0. The eNB may estimate theuplink timing from the random access preamble transmitted by thewireless device. The TA command may be derived by the eNB based on theestimation of the difference between the desired UL timing and theactual UL timing. The wireless device may determine the initial uplinktransmission timing relative to the corresponding downlink of the sTAGon which the preamble is transmitted.

The mapping of a serving cell to a TAG may be configured by a servingeNB with RRC signaling. The mechanism for TAG configuration andreconfiguration may be based on RRC signaling. If an eNB performs anSCell addition configuration, the related TAG configuration may beconfigured for the SCell. An eNB may modify the TAG configuration of anSCell by removing (e.g., releasing) the SCell and adding (e.g.,configuring) a new SCell (with the same physical cell ID and frequency)with an updated TAG ID. The new SCell with the updated TAG ID mayinitially be inactive subsequent to being assigned the updated TAG ID.The eNB may activate the updated new SCell and start scheduling packetson the activated SCell. In some examples, it may not be possible tochange the TAG associated with an SCell, but rather, the SCell may needto be removed and a new SCell may need to be added with another TAG. Forexample, if there is a need to move an SCell from an sTAG to a pTAG, atleast one RRC message, such as at least one RRC reconfiguration message,may be sent to the wireless device. The at least one RRC message may besent to the wireless device to reconfigure TAG configurations, forexample, by releasing the SCell and configuring the SCell as a part ofthe pTAG. If, for example, an SCell is added or configured without a TAGindex, the SCell may be explicitly assigned to the pTAG. The PCell maynot change its TA group and may be a member of the pTAG.

In LTE Release-10 and Release-11 CA, a PUCCH transmission is onlytransmitted on a PCell (e.g., a PSCell) to an eNB. In LTE-Release 12 andearlier, a wireless device may transmit PUCCH information on one cell(e.g., a PCell or a PSCell) to a given eNB. As the number of CA capablewireless devices increase, and as the number of aggregated carriersincrease, the number of PUCCHs and the PUCCH payload size may increase.Accommodating the PUCCH transmissions on the PCell may lead to a highPUCCH load on the PCell. A PUCCH on an SCell may be used to offload thePUCCH resource from the PCell. More than one PUCCH may be configured.For example, a PUCCH on a PCell may be configured and another PUCCH onan SCell may be configured. One, two, or more cells may be configuredwith PUCCH resources for transmitting CSI, acknowledgment (ACK), and/ornon-acknowledgment (NACK) to a base station. Cells may be grouped intomultiple PUCCH groups, and one or more cell within a group may beconfigured with a PUCCH. In some examples, one SCell may belong to onePUCCH group. SCells with a configured PUCCH transmitted to a basestation may be called a PUCCH SCell, and a cell group with a commonPUCCH resource transmitted to the same base station may be called aPUCCH group.

A MAC entity may have a configurable timer, for example,timeAlignmentTimer, per TAG. The timeAlignmentTimer may be used tocontrol how long the MAC entity considers the serving cells belonging tothe associated TAG to be uplink time aligned. If a Timing AdvanceCommand MAC control element is received, the MAC entity may apply theTiming Advance Command for the indicated TAG; and/or the MAC entity maystart or restart the timeAlignmentTimer associated with a TAG that maybe indicated by the Timing Advance Command MAC control element. If aTiming Advance Command is received in a Random Access Response messagefor a serving cell belonging to a TAG, the MAC entity may apply theTiming Advance Command for this TAG and/or start or restart thetimeAlignmentTimer associated with this TAG. Additionally oralternatively, if the Random Access Preamble is not selected by the MACentity, the MAC entity may apply the Timing Advance Command for this TAGand/or start or restart the timeAlignmentTimer associated with this TAG.If the timeAlignmentTimer associated with this TAG is not running, theTiming Advance Command for this TAG may be applied, and thetimeAlignmentTimer associated with this TAG may be started. If thecontention resolution is not successful, a timeAlignmentTimer associatedwith this TAG may be stopped. If the contention resolution issuccessful, the MAC entity may ignore the received Timing AdvanceCommand. The MAC entity may determine whether the contention resolutionis successful or whether the contention resolution is not successful.

FIG. 10A and FIG. 10B show examples for interfaces between a 5G corenetwork (e.g., NGC) and base stations (e.g., gNB and eLTE eNB). A basestation, such as a gNB 1020, may be interconnected to an NGC 1010control plane employing an NG-C interface. The base station, forexample, the gNB 1020, may also be interconnected to an NGC 1010 userplane (e.g., UPGW) employing an NG-U interface. As another example, abase station, such as an eLTE eNB 1040, may be interconnected to an NGC1030 control plane employing an NG-C interface. The base station, forexample, the eLTE eNB 1040, may also be interconnected to an NGC 1030user plane (e.g., UPGW) employing an NG-U interface. An NG interface maysupport a many-to-many relation between 5G core networks and basestations.

FIG. 11A, FIG. 11B, FIG. 11C, FIG. 11D, FIG. 11E, and FIG. 11F areexamples for architectures of tight interworking between a 5G RAN and anLTE RAN. The tight interworking may enable a multiplereceiver/transmitter (RX/TX) wireless device in an RRC_CONNECTED stateto be configured to utilize radio resources provided by two schedulerslocated in two base stations (e.g., an eLTE eNB and a gNB). The two basestations may be connected via a non-ideal or ideal backhaul over the Xxinterface between an LTE eNB and a gNB, or over the Xn interface betweenan eLTE eNB and a gNB. Base stations involved in tight interworking fora certain wireless device may assume different roles. For example, abase station may act as a master base station or a base station may actas a secondary base station. In tight interworking, a wireless devicemay be connected to both a master base station and a secondary basestation. Mechanisms implemented in tight interworking may be extended tocover more than two base stations.

A master base station may be an LTE eNB 1102A or an LTE eNB 1102B, whichmay be connected to EPC nodes 1101A or 1101B, respectively. Thisconnection to EPC nodes may be, for example, to an MME via the S1-Cinterface and/or to an S-GW via the S1-U interface. A secondary basestation may be a gNB 1103A or a gNB 1103B, either or both of which maybe a non-standalone node having a control plane connection via an Xx-Cinterface to an LTE eNB (e.g., the LTE eNB 1102A or the LTE eNB 1102B).In the tight interworking architecture of FIG. 11A, a user plane for agNB (e.g., the gNB 1103A) may be connected to an S-GW (e.g., the EPC1101A) through an LTE eNB (e.g., the LTE eNB 1102A), via an Xx-Uinterface between the LTE eNB and the gNB, and via an S1-U interfacebetween the LTE eNB and the S-GW. In the architecture of FIG. 11B, auser plane for a gNB (e.g., the gNB 1103B) may be connected directly toan S-GW (e.g., the EPC 1101B) via an S1-U interface between the gNB andthe S-GW.

A master base station may be a gNB 1103C or a gNB 1103D, which may beconnected to NGC nodes 1101C or 1101D, respectively. This connection toNGC nodes may be, for example, to a control plane core node via the NG-Cinterface and/or to a user plane core node via the NG-U interface. Asecondary base station may be an eLTE eNB 1102C or an eLTE eNB 1102D,either or both of which may be a non-standalone node having a controlplane connection via an Xn-C interface to a gNB (e.g., the gNB 1103C orthe gNB 1103D). In the tight interworking architecture of FIG. 11C, auser plane for an eLTE eNB (e.g., the eLTE eNB 1102C) may be connectedto a user plane core node (e.g., the NGC 1101C) through a gNB (e.g., thegNB 1103C), via an Xn-U interface between the eLTE eNB and the gNB, andvia an NG-U interface between the gNB and the user plane core node. Inthe architecture of FIG. 11D, a user plane for an eLTE eNB (e.g., theeLTE eNB 1102D) may be connected directly to a user plane core node(e.g., the NGC 1101D) via an NG-U interface between the eLTE eNB and theuser plane core node.

A master base station may be an eLTE eNB 1102E or an eLTE eNB 1102F,which may be connected to NGC nodes 1101E or 1101F, respectively. Thisconnection to NGC nodes may be, for example, to a control plane corenode via the NG-C interface and/or to a user plane core node via theNG-U interface. A secondary base station may be a gNB 1103E or a gNB1103F, either or both of which may be a non-standalone node having acontrol plane connection via an Xn-C interface to an eLTE eNB (e.g., theeLTE eNB 1102E or the eLTE eNB 1102F). In the tight interworkingarchitecture of FIG. 11E, a user plane for a gNB (e.g., the gNB 1103E)may be connected to a user plane core node (e.g., the NGC 1101E) throughan eLTE eNB (e.g., the eLTE eNB 1102E), via an Xn-U interface betweenthe eLTE eNB and the gNB, and via an NG-U interface between the eLTE eNBand the user plane core node. In the architecture of FIG. 11F, a userplane for a gNB (e.g., the gNB 1103F) may be connected directly to auser plane core node (e.g., the NGC 1101F) via an NG-U interface betweenthe gNB and the user plane core node.

FIG. 12A, FIG. 12B, and FIG. 12C are examples for radio protocolstructures of tight interworking bearers.

An LTE eNB 1201A may be an S1 master base station, and a gNB 1210A maybe an S1 secondary base station. An example for a radio protocolarchitecture for a split bearer and an SCG bearer is shown. The LTE eNB1201A may be connected to an EPC with a non-standalone gNB 1210A, via anXx interface between the PDCP 1206A and an NR RLC 1212A. The LTE eNB1201A may include protocol layers MAC 1202A, RLC 1203A and RLC 1204A,and PDCP 1205A and PDCP 1206A. An MCG bearer type may interface with thePDCP 1205A, and a split bearer type may interface with the PDCP 1206A.The gNB 1210A may include protocol layers NR MAC 1211A, NR RLC 1212A andNR RLC 1213A, and NR PDCP 1214A. An SCG bearer type may interface withthe NR PDCP 1214A.

A gNB 1201B may be an NG master base station, and an eLTE eNB 1210B maybe an NG secondary base station. An example for a radio protocolarchitecture for a split bearer and an SCG bearer is shown. The gNB1201B may be connected to an NGC with a non-standalone eLTE eNB 1210B,via an Xn interface between the NR PDCP 1206B and an RLC 1212B. The gNB1201B may include protocol layers NR MAC 1202B, NR RLC 1203B and NR RLC1204B, and NR PDCP 1205B and NR PDCP 1206B. An MCG bearer type mayinterface with the NR PDCP 1205B, and a split bearer type may interfacewith the NR PDCP 1206B. The eLTE eNB 1210B may include protocol layersMAC 1211B, RLC 1212B and RLC 1213B, and PDCP 1214B. An SCG bearer typemay interface with the PDCP 1214B.

An eLTE eNB 1201C may be an NG master base station, and a gNB 1210C maybe an NG secondary base station. An example for a radio protocolarchitecture for a split bearer and an SCG bearer is shown. The eLTE eNB1201C may be connected to an NGC with a non-standalone gNB 1210C, via anXn interface between the PDCP 1206C and an NR RLC 1212C. The eLTE eNB1201C may include protocol layers MAC 1202C, RLC 1203C and RLC 1204C,and PDCP 1205C and PDCP 1206C. An MCG bearer type may interface with thePDCP 1205C, and a split bearer type may interface with the PDCP 1206C.The gNB 1210C may include protocol layers NR MAC 1211C, NR RLC 1212C andNR RLC 1213C, and NR PDCP 1214C. An SCG bearer type may interface withthe NR PDCP 1214C.

In a 5G network, the radio protocol architecture that a particularbearer uses may depend on how the bearer is setup. At least threealternatives may exist, for example, an MCG bearer, an SCG bearer, and asplit bearer, such as shown in FIG. 12A, FIG. 12B, and FIG. 12C. The NRRRC may be located in a master base station, and the SRBs may beconfigured as an MCG bearer type and may use the radio resources of themaster base station. Tight interworking may have at least one bearerconfigured to use radio resources provided by the secondary basestation. Tight interworking may or may not be configured or implemented.

The wireless device may be configured with two MAC entities: e.g., oneMAC entity for a master base station, and one MAC entity for a secondarybase station. In tight interworking, the configured set of serving cellsfor a wireless device may comprise of two subsets: e.g., the Master CellGroup (MCG) including the serving cells of the master base station, andthe Secondary Cell Group (SCG) including the serving cells of thesecondary base station.

At least one cell in a SCG may have a configured UL CC and one of them,for example, a PSCell (or the PCell of the SCG, which may also be calleda PCell), is configured with PUCCH resources. If the SCG is configured,there may be at least one SCG bearer or one split bearer. If one or moreof a physical layer problem or a random access problem is detected on aPSCell, if the maximum number of (NR) RLC retransmissions associatedwith the SCG has been reached, and/or if an access problem on a PSCellduring an SCG addition or during an SCG change is detected, then: an RRCconnection re-establishment procedure may not be triggered, ULtransmissions towards cells of the SCG may be stopped, a master basestation may be informed by the wireless device of a SCG failure type,and/or for a split bearer the DL data transfer over the master basestation may be maintained. The RLC AM bearer may be configured for thesplit bearer. Like the PCell, a PSCell may not be de-activated. A PSCellmay be changed with an SCG change, for example, with security key changeand a RACH procedure. A direct bearer type change, between a splitbearer and an SCG bearer, may not be supported. Simultaneousconfiguration of an SCG and a split bearer may not be supported.

A master base station and a secondary base station may interact. Themaster base station may maintain the RRM measurement configuration ofthe wireless device. The master base station may determine to ask asecondary base station to provide additional resources (e.g., servingcells) for a wireless device. This determination may be based on, forexample, received measurement reports, traffic conditions, and/or bearertypes. If a request from the master base station is received, asecondary base station may create a container that may result in theconfiguration of additional serving cells for the wireless device, orthe secondary base station may determine that it has no resourceavailable to do so. The master base station may provide at least part ofthe AS configuration and the wireless device capabilities to thesecondary base station, for example, for wireless device capabilitycoordination. The master base station and the secondary base station mayexchange information about a wireless device configuration such as byusing RRC containers (e.g., inter-node messages) carried in Xn or Xxmessages. The secondary base station may initiate a reconfiguration ofits existing serving cells (e.g., PUCCH towards the secondary basestation). The secondary base station may determine which cell is thePSCell within the SCG. The master base station may not change thecontent of the RRC configuration provided by the secondary base station.If an SCG is added and/or an SCG SCell is added, the master base stationmay provide the latest measurement results for the SCG cell(s). Eitheror both of a master base station and a secondary base station may knowthe SFN and subframe offset of each other by OAM, (e.g., for the purposeof DRX alignment and identification of a measurement gap). If a new SCGSCell is added, dedicated RRC signaling may be used for sending requiredsystem information of the cell, such as for CA, except, for example, forthe SFN acquired from an MIB of the PSCell of an SCG.

FIG. 13A and FIG. 13B show examples for gNB deployment. A core 1301 anda core 1310 may interface with other nodes via RAN-CN interfaces. In anon-centralized deployment example, the full protocol stack (e.g., NRRRC, NR PDCP, NR RLC, NR MAC, and NR PHY) may be supported at one node,such as a gNB 1302, a gNB 1303, and/or an eLTE eNB or LTE eNB 1304.These nodes (e.g., the gNB 1302, the gNB 1303, and the eLTE eNB or LTEeNB 1304) may interface with one of more of each other via a respectiveinter-BS interface. In a centralized deployment example, upper layers ofa gNB may be located in a Central Unit (CU) 1311, and lower layers ofthe gNB may be located in Distributed Units (DU) 1312, 1313, and 1314.The CU-DU interface (e.g., Fs interface) connecting CU 1311 and DUs1312, 1312, and 1314 may be ideal or non-ideal. The Fs-C may provide acontrol plane connection over the Fs interface, and the Fs-U may providea user plane connection over the Fs interface. In the centralizeddeployment, different functional split options between the CU 1311 andthe DUs 1312, 1313, and 1314 may be possible by locating differentprotocol layers (e.g., RAN functions) in the CU 1311 and in the DU 1312,1313, and 1314. The functional split may support flexibility to move theRAN functions between the CU 1311 and the DUs 1312, 1313, and 1314depending on service requirements and/or network environments. Thefunctional split option may change during operation (e.g., after the Fsinterface setup procedure), or the functional split option may changeonly in the Fs setup procedure (e.g., the functional split option may bestatic during operation after Fs setup procedure).

FIG. 14 shows examples for different functional split options of acentralized gNB deployment. Element numerals that are followed by “A” or“B” designations in FIG. 14 may represent the same elements in differenttraffic flows, for example, either receiving data (e.g., data 1402A) orsending data (e.g., 1402B). In the split option example 1, an NR RRC1401 may be in a CU, and an NR PDCP 1403, an NR RLC (e.g., comprising aHigh NR RLC 1404 and/or a Low NR RLC 1405), an NR MAC (e.g., comprisinga High NR MAC 1406 and/or a Low NR MAC 1407), an NR PHY (e.g.,comprising a High NR PHY 1408 and/or a LOW NR PHY 1409), and an RF 1410may be in a DU. In the split option example 2, the NR RRC 1401 and theNR PDCP 1403 may be in a CU, and the NR RLC, the NR MAC, the NR PHY, andthe RF 1410 may be in a DU. In the split option example 3, the NR RRC1401, the NR PDCP 1403, and a partial function of the NR RLC (e.g., theHigh NR RLC 1404) may be in a CU, and the other partial function of theNR RLC (e.g., the Low NR RLC 1405), the NR MAC, the NR PHY, and the RF1410 may be in a DU. In the split option example 4, the NR RRC 1401, theNR PDCP 1403, and the NR RLC may be in a CU, and the NR MAC, the NR PHY,and the RF 1410 may be in a DU. In the split option example 5, the NRRRC 1401, the NR PDCP 1403, the NR RLC, and a partial function of the NRMAC (e.g., the High NR MAC 1406) may be in a CU, and the other partialfunction of the NR MAC (e.g., the Low NR MAC 1407), the NR PHY, and theRF 1410 may be in a DU. In the split option example 6, the NR RRC 1401,the NR PDCP 1403, the NR RLC, and the NR MAC may be in CU, and the NRPHY and the RF 1410 may be in a DU. In the split option example 7, theNR RRC 1401, the NR PDCP 1403, the NR RLC, the NR MAC, and a partialfunction of the NR PHY (e.g., the High NR PHY 1408) may be in a CU, andthe other partial function of the NR PHY (e.g., the Low NR PHY 1409) andthe RF 1410 may be in a DU. In the split option example 8, the NR RRC1401, the NR PDCP 1403, the NR RLC, the NR MAC, and the NR PHY may be ina CU, and the RF 1410 may be in a DU.

The functional split may be configured per CU, per DU, per wirelessdevice, per bearer, per slice, and/or with other granularities. In a perCU split, a CU may have a fixed split, and DUs may be configured tomatch the split option of the CU. In a per DU split, each DU may beconfigured with a different split, and a CU may provide different splitoptions for different DUs. In a per wireless device split, a gNB (e.g.,a CU and a DU) may provide different split options for differentwireless devices. In a per bearer split, different split options may beutilized for different bearer types. In a per slice splice, differentsplit options may be applied for different slices.

A new radio access network (new RAN) may support different networkslices, which may allow differentiated treatment customized to supportdifferent service requirements with end to end scope. The new RAN mayprovide a differentiated handling of traffic for different networkslices that may be pre-configured, and the new RAN may allow a singleRAN node to support multiple slices. The new RAN may support selectionof a RAN part for a given network slice, for example, by one or moreslice ID(s) or NSSAI(s) provided by a wireless device or provided by anNGC (e.g., an NG CP). The slice ID(s) or NSSAI(s) may identify one ormore of pre-configured network slices in a PLMN. For an initial attach,a wireless device may provide a slice ID and/or an NSSAI, and a RAN node(e.g., a gNB) may use the slice ID or the NSSAI for routing an initialNAS signaling to an NGC control plane function (e.g., an NG CP). If awireless device does not provide any slice ID or NSSAI, a RAN node maysend a NAS signaling to a default NGC control plane function. Forsubsequent accesses, the wireless device may provide a temporary ID fora slice identification, which may be assigned by the NGC control planefunction, to enable a RAN node to route the NAS message to a relevantNGC control plane function. The new RAN may support resource isolationbetween slices. If the RAN resource isolation is implemented, shortageof shared resources in one slice does not cause a break in a servicelevel agreement for another slice.

The amount of data traffic carried over networks is expected to increasefor many years to come. The number of users and/or devices is increasingand each user/device accesses an increasing number and variety ofservices, for example, video delivery, large files, and images. Thisrequires not only high capacity in the network, but also provisioningvery high data rates to meet customers' expectations on interactivityand responsiveness. More spectrum may be required for network operatorsto meet the increasing demand. Considering user expectations of highdata rates along with seamless mobility, it is beneficial that morespectrum be made available for deploying macro cells as well as smallcells for communication systems.

Striving to meet the market demands, there has been increasing interestfrom operators in deploying some complementary access utilizingunlicensed spectrum to meet the traffic growth. This is exemplified bythe large number of operator-deployed Wi-Fi networks and the 3GPPstandardization of LTE/WLAN interworking solutions. This interestindicates that unlicensed spectrum, if present, may be an effectivecomplement to licensed spectrum for network operators, for example, tohelp address the traffic explosion in some examples, such as hotspotareas. Licensed Assisted Access (LAA) offers an alternative foroperators to make use of unlicensed spectrum, for example, if managingone radio network, offering new possibilities for optimizing thenetwork's efficiency.

Listen-before-talk (clear channel assessment) may be implemented fortransmission in an LAA cell. In a listen-before-talk (LBT) procedure,equipment may apply a clear channel assessment (CCA) check before usingthe channel. For example, the CCA may utilize at least energy detectionto determine the presence or absence of other signals on a channel todetermine if a channel is occupied or clear, respectively. For example,European and Japanese regulations mandate the usage of LBT in theunlicensed bands. Apart from regulatory requirements, carrier sensingvia LBT may be one way for fair sharing of the unlicensed spectrum.

Discontinuous transmission on an unlicensed carrier with limited maximumtransmission duration may be enabled. Some of these functions may besupported by one or more signals to be transmitted from the beginning ofa discontinuous LAA downlink transmission. Channel reservation may beenabled by the transmission of signals, by an LAA node, after gainingchannel access, for example, via a successful LBT operation, so thatother nodes that receive the transmitted signal with energy above acertain threshold sense the channel to be occupied. Functions that mayneed to be supported by one or more signals for LAA operation withdiscontinuous downlink transmission may include one or more of thefollowing: detection of the LAA downlink transmission (including cellidentification) by wireless devices, time synchronization of wirelessdevices, and frequency synchronization of wireless devices.

DL LAA design may employ subframe boundary alignment according to LTE-Acarrier aggregation timing relationships across serving cells aggregatedby CA. This may not indicate that the eNB transmissions may start onlyat the subframe boundary. LAA may support transmitting PDSCH if not allOFDM symbols are available for transmission in a subframe according toLBT. Delivery of necessary control information for the PDSCH may also besupported.

LBT procedures may be employed for fair and friendly coexistence of LAAwith other operators and technologies operating in unlicensed spectrum.LBT procedures on a node attempting to transmit on a carrier inunlicensed spectrum may require the node to perform a clear channelassessment to determine if the channel is free for use. An LBT proceduremay involve at least energy detection to determine if the channel isbeing used. For example, regulatory requirements in some regions, forexample, in Europe, specify an energy detection threshold such that if anode receives energy greater than this threshold, the node assumes thatthe channel is not free. Nodes may follow such regulatory requirements.A node may optionally use a lower threshold for energy detection thanthat specified by regulatory requirements. LAA may employ a mechanism toadaptively change the energy detection threshold, for example, LAA mayemploy a mechanism to adaptively lower the energy detection thresholdfrom an upper bound. Adaptation mechanism may not preclude static orsemi-static setting of the threshold. A Category 4 LBT mechanism orother type of LBT mechanisms may be implemented.

Various example LBT mechanisms may be implemented. For some signals, insome implementation scenarios, in some situations, and/or in somefrequencies, no LBT procedure may performed by the transmitting entity.For example, Category 2 (e.g., LBT without random back-off) may beimplemented. The duration of time that the channel is sensed to be idlebefore the transmitting entity transmits may be deterministic. Forexample, Category 3 (e.g., LBT with random back-off with a contentionwindow of fixed size) may be implemented. The LBT procedure may have thefollowing procedure as one of its components. The transmitting entitymay draw a random number N within a contention window. The size of thecontention window may be specified by the minimum and maximum value ofN. The size of the contention window may be fixed. The random number Nmay be employed in the LBT procedure to determine the duration of timethat the channel is sensed to be idle, for example, before thetransmitting entity transmits on the channel. For example, Category 4(e.g., LBT with random back-off with a contention window of variablesize) may be implemented. The transmitting entity may draw a randomnumber N within a contention window. The size of contention window maybe specified by the minimum and maximum value of N. The transmittingentity may vary the size of the contention window if drawing the randomnumber N. The random number N may be used in the LBT procedure todetermine the duration of time that the channel is sensed to be idle,for example, before the transmitting entity transmits on the channel.

LAA may employ uplink LBT at the wireless device. The UL LBT scheme maybe different from the DL LBT scheme, for example, by using different LBTmechanisms or parameters. These differences in schemes may be due to theLAA UL being based on scheduled access, which may affect a wirelessdevice's channel contention opportunities. Other considerationsmotivating a different UL LBT scheme may include, but are not limitedto, multiplexing of multiple wireless devices in a single subframe.

LAA may use uplink LBT at the wireless device. The UL LBT scheme may bedifferent from the DL LBT scheme, for example, by using different LBTmechanisms or parameters. These differences in schemes may be due to theLAA UL being based on scheduled access, which may affect a wirelessdevice's channel contention opportunities. Other considerationsmotivating a different UL LBT scheme may include, but are not limitedto, multiplexing of multiple wireless devices in a single subframe.

A DL transmission burst may be a continuous transmission from a DLtransmitting node, for example, with no transmission immediately beforeor after from the same node on the same CC. An UL transmission burstfrom a wireless device perspective may be a continuous transmission froma wireless device, for example, with no transmission immediately beforeor after from the same wireless device on the same CC. A UL transmissionburst may be defined from a wireless device perspective or from an eNBperspective. If an eNB is operating DL and UL LAA over the sameunlicensed carrier, DL transmission burst(s) and UL transmissionburst(s) on LAA may be scheduled in a TDM manner over the sameunlicensed carrier. An instant in time may be part of a DL transmissionburst or part of an UL transmission burst.

A base station may configure a wireless device for uplink transmissionswithout a grant (e.g., grant free uplink transmissions). Resources foruplink transmission without grant may be semi-statically configuredand/or reconfigured. A resource configuration may comprise at least:physical resources in a time domain and/or frequency domain, and/orreference signal (RS) parameters. The configuration parameters maycomprise at least modulation and coding scheme (MCS), redundancyversion, and/or a number of repetitions (K). A wireless device may beconfigured with multiple K values. One or more RSs may be transmittedwith data, for example, for an uplink transmission without grant. Thesame channel structure as grant-based transmission may be used foruplink transmissions without grant. A common DMRS structure may be usedfor downlink and uplink, such as for CP-OFDM.K repetitions, includinginitial transmission may be used. K repetitions for the same transportblock may be with or without the same RV and/or with or without the sameMCS. K repetitions may be used, for example, for an uplink transmissionwith and/or without grant. Frequency hopping may be used, for example,between an initial transmission and a retransmission, and/or betweenretransmissions. A wireless device may continue repetitions for a TBuntil either an acknowledgement (ACK) is successfully received from abase station or the number of repetitions for the TB reaches K. Awireless device may continue such repetitions for the TB, for example,for uplink transmissions without grant. A wireless device may continuerepetitions for a TB (e.g., where the wireless device may be configuredwith K repetitions for a TB transmission with and/or without grant):until an uplink grant is successfully received for a slot, and/or amini-slot, for the same TB; an acknowledgement and/or indication of asuccessful receiving of the TB from a base station; and/or the number ofrepetitions for the TB reaches K. A wireless device may be identifiedbased on an RS sequence and/or configuration for the wireless device,and/or radio resources configured for uplink transmission. Additionallyor alternatively, a wireless device ID may be based on an RS sequenceand/or configuration for the wireless device, and/or radio resourcesconfigured for uplink transmission.

Time and frequency resources for uplink transmission without grant maybe configured in a wireless device-specific manner. A network mayconfigure the same time and/or frequency resource, and/or RS parameters,for multiple wireless devices. A base station may avoid collision withsuch a network implementation. The base station may identify a wirelessdevice ID, for example, based on physical layer parameters such as timeand/or frequency resources, and/or RS (e.g., DMRS) resources and/orparameters. One or both of DFT-S-OFDM and CP-OFDM may be supported, forexample, for uplink transmission without grant. Uplink transmissionwithout grant may support one or more HARQ processes. HARQ process IDmay be identified, for example, based on resources used for uplinktransmission without grant, such as time and/or frequency resourcesand/or RS parameters for HARQ process ID identification. Such HARQprocess ID identification may be used for one or both of transmissionwith grant and transmission without grant.

A wireless device may be configured with a plurality of parameters foruplink data transmission without grant. The wireless device may beconfigured with one or more of: a reference symbol, and/or time and/orfrequency resources. The wireless device may be configured in a wirelessdevice-specific manner. The time and/or frequency resources configuredfor a wireless device may or may not collide with those of anotherwireless device. DFT-S-OFDM and/or CP-OFDM may be supported, such as foruplink transmission without grant. Uplink transmission without grant maysupport a plurality of HARQ processes. L1 signaling may be used foractivation and/or deactivation of uplink transmission without grant. L1signaling may be used for modification of parameters that may beconfigured, for example, by RRC signaling. Example parameters maycomprise time domain resource allocation (e.g., for one transmission),frequency domain resource allocation (e.g., in terms of RBs or RBGs),wireless device-specific DMRS configuration, MCS/TBS, etc. L1 signalingmay be used for switching to and/or from grant-based re-transmission forthe same TB. The L1 signaling may be based on wireless device-specificDCI (e.g., uplink grant) and/or a group common DCI. RRC configurationand/or reconfiguration of a set of resource and parameters may comprisetransmission interval, physical resources such as time domain resourceallocation (e.g., for one transmission), frequency domain resourceallocation (e.g., in terms of RBs or RBG(s)), wireless device-specificDMRS configuration, etc. A plurality of physical resources may beconfigured in the transmission interval. One or more repetitions of asame one or more TBs may be performed (e.g., during the transmissioninterval) after an initial transmission. A repetition in the one or morerepetitions may be performed in the same resource configured for initialtransmission. A repetition in the one or more repetitions may be may bein a different resource than the initial transmission. The radioresources configured for initial transmission and repetition may or maynot be timely contiguous.

Uplink transmission without grant may be configured and/or activatedwith a plurality of types. In a first type, UL data transmission withoutgrant may be activated and/or deactivated based on RRC configuration,and/or reconfiguration, without L1 signaling. In a second type, UL datatransmission without grant may be based on both RRC configuration and L1signaling for activation and/or deactivation. In a third type, UL datatransmission without grant may be based on RRC configuration and mayallow L1 signaling to modify some parameters configured by RRCsignaling. For the first type of UL data transmission without grant, theRRC configuration and/or reconfiguration may comprise periodicity andoffset of a resource with respect to one or more of: SFN=0, time domainresource allocation, frequency domain resource allocation, wirelessdevice-specific DMRS configuration, MCS and/or TBS, number ofrepetitions K, power control related parameters, HARQ relatedparameters, etc. For the second type of UL transmission without grant,some parameters, for example, periodicity and/or power control relatedparameters, may be RRC configured. For the second type of ULtransmission without grant, the parameters that may not be RRCconfigured and/or required to be updated (e.g., an offset value withrespect to a timing reference, time domain resource allocation,frequency domain resource allocation, wireless device-specific DMRSconfiguration, and/or MCS and/or TBS) may be indicated by L1 signaling.The number of repetitions K may be RRC configured and/or indicated by L1signaling.

An uplink grant, a group-common DCI, and/or a HARQ feedback indicationmechanism used for an uplink transmission without grant may indicate anACK or NACK implicitly or explicitly, which may reduce a signalingoverhead and/or fulfill one or more service requirements (e.g., URLLC).An uplink grant may indicate an ACK for an uplink transmission withoutgrant, for example, after or in response to the uplink transmissionwithout grant. The uplink grant may be a dynamic grant, which may be forthe same HARQ process as the uplink transmission without grant. Anuplink grant for a new data transmission may implicitly indicate an ACKfor an uplink transmission without grant. An uplink grant for the sameTB initially transmitted without grant may indicate NACK for an uplinktransmission without grant.

A group-common DCI may be used to indicate one or more HARQ feedbacks ofone or more wireless devices, such as for uplink transmission withoutgrant. The group common DCI may indicate an ACK. Additionally oralternatively, the group common DCI may indicate a NACK. Additionally oralternatively, the group common DCI may indicate an ACK and/or a NACK.

The wireless device may use a timer, for example, to determine animplicit and/or explicit HARQ feedback (e.g., ACK and/or NACK) that maycorrespond to an uplink transmission without grant. A timer value may beconfigured for the wireless device, for example, via RRC signaling. Thewireless device may receive one or more RRC message indicating the timervalue. The wireless device may start and/or restart the timer, forexample, after or in response to an uplink transmission without grant(e.g., one or more TBs corresponding to an uplink transmission withoutgrant). The wireless device may assume or determine an ACK occurrenceafter or in response to the timer expiring and the wireless device notreceiving a NACK (e.g., after K repetitions). The wireless device mayassume or determine a NACK occurrence after or in response to the timerexpiring and the wireless device not receiving an ACK. The wirelessdevice may assume or determine a NACK occurrence corresponding to anuplink transmission without grant after or in response to receiving agrant (e.g., dynamic grant) for retransmission of the same one or moreTBs in a first uplink transmission without grant (e.g., the same HARQprocess and with NDI not indicating a switch). The wireless device mayassume or determine a NACK occurrence corresponding to an uplinktransmission without grant after or in response to receiving a grant(e.g., a dynamic grant) for retransmission of the same one or more TB ina first uplink transmission without grant in a period of time. Theperiod of time may be configured for the wireless device. The wirelessdevice may receive an RRC message indicating the period of time. Theperiod of time may be pre-configured. The period of time may beindicated and/or updated by L1 signaling.

A base station may configure a wireless device with one or more RNTIs,such as for uplink transmission without grant. The base station mayconfigure a RNTI for uplink transmission without grant perconfiguration, per service, per type (e.g., the first, second, and/orthird types), and/or per a wireless device. The base station mayconfigure a wireless device with a first RNTI. The first RNTI may be agroup-common RNTI. The base station may transmit downlink controlinformation (DCI) (e.g., a group common DCI) corresponding to the firstRNTI. The base station may use the DCI for indicating HARQ feedback(e.g., ACK and/or NACK) that may correspond to one or more uplinktransmissions (e.g., one or more TBs corresponding to one or more uplinktransmission) without uplink grant (e.g., for semi-persistent scheduling(SPS) and/or grant-free resource configuration) for one or more wirelessdevices. The DCI may be scrambled, for example, based on the first RNTI.The wireless device may monitor a common search space to detect the DCIcorresponding to the first RNTI. The base station may transmit and/orindicate NACK (e.g., using the DCI) corresponding to one or more TBs ofthe wireless device. The wireless device may assume or determine an ACKoccurrence (e.g., implicit ACK) if no NACK is received within a periodof time. The base station may transmit and/or indicate an ACK (e.g.,using the DCI), and the wireless device may assume or determine a NACKoccurrence (e.g., implicit NACK), if no ACK is received within a periodof time. The period of time may be configured for the wireless device.The base station may transmit an RRC message indicating the period oftime. The period of time may be pre-configured. The wireless device maytransmit up to a first number of repetitions of a same one or more TBscorresponding to an uplink transmission without grant. The period oftime may or may not be based on the duration that the first number ofrepetitions (e.g., of the same one or more TBs corresponding to theuplink transmission) is received. The wireless device may monitor forthe DCI at least for a portion of the period of time. The wirelessdevice may stop monitoring the DCI, for example, after or in response toreceiving the ACK and/or NACK corresponding to the uplink transmissionwithout grant. The DCI may comprise an ACK and/or a NACK for a pluralityof wireless devices. The plurality of wireless devices may be configuredwith the same first RNTI used for transmission of the DCI. The pluralityof wireless devices configured with the same first RNTI may monitor thesearch space, detect the same DCI, and/or identify HARQ feedbackcorresponding to their transmissions. The DCI may comprise a pluralityof HARQ feedbacks (e.g., corresponding to a plurality of TBs) for thesame wireless device. The mapping between a HARQ feedback and acorresponding wireless device, and/or the mapping between a HARQfeedback and a TB in a plurality of TBs transmitted by a wirelessdevice, may be based on a rule, implicitly indicated by the DCI, and/orexplicitly indicated by the DCI.

Uplink demodulation reference signals (DMRS) may be used for channelestimation and/or coherent demodulation of PUSCH and PUCCH. A basestation may configure a wireless device with DMRS configurationparameters. The wireless device may receive one or more RRC messages.The one or more RRC messages may comprise a DMRS-Config IE. TheDMRS-Config IE may comprise DMRS configuration parameters. TheDMRS-Config configuration may be enhanced and/or the DMRS-Configconfiguration parameters may be enhanced. A DMRS-Config IE may berepresented as follows:

  DMRS-Config-r11 ::=  CHOICE {  release  NULL,  setup  SEQUENCE {scramblingIdentity-r11  INTEGER (0..503), scramblingIdentity2-r11 INTEGER (0..503)  } } DMRS-Config-v1310 ::= SEQUENCE {dmrs-tableAlt-r13   ENUMERATED {true} OPTIONAL -- Need OR }

Parameters scramblingIdentity and/or scramblingIdentity2 may indicate aparameter n^(DMRS,i) _(ID). The parameter, dmrs-tableAlt may indicatewhether to use an alternative table for DMRS, for example, upon PDSCHtransmission.

An uplink (UL) transmission without a dynamic UL grant, which may bereferred to as a grant-free (GF) UL transmission or a configured granttransmission, may be supported. Configured grant transmissions may besupported for one or more service types, including, for example, URLLC.A base station may allocate to a wireless device one or more configuredgrant radio resources. The wireless device may be configured by the basestation to use the configured grant radio resources to transmit, via theconfigured grant radio resources without a dynamic UL grant, one or moredata packets. By using configured grant radio resources, without adynamic UL grant, a wireless device may be able to reduce signalingoverhead relative to a grant-based (GB) UL transmission. A service typethat may have strict requirements, for example in terms of latency andreliability, such as in URLLC, may be a candidate for which a basestation may configure a wireless device with the configured granttransmission. The wireless device configured with the configured grantradio resource may skip a UL transmission via the configured grant radioresource, for example, if the wireless device does not have data totransmit.

Configured grant transmission may support multiple wireless devices toaccess the same configured grant radio resources (e.g., a GF radioresource pool), which may reduce latency, and reduce signaling overhead,relative a GB UL transmission. A GF radio resource pool may comprise asubset of one or more radio resources from a common radio resource set(e.g., from all uplink shared channel radio resources). A GF radioresource pool may be used to allocate exclusive, or partiallyoverlapped, one or more radio resources for configured granttransmissions in a cell. A GF resource pool may be used to organizefrequency and/or time reuse between different cells or parts of a cell(e.g., at a cell-center and/or at a cell-edge).

A collision may occur between configured grant transmissions of two ormore wireless devices, for example, if a base station configuresmultiple wireless devices with the same (or partially overlapped) GFradio resource pool. The base station may configure one or moreparameters to assign a wireless device specific demodulation referencesignal (DMRS), along with the GF radio resource pool configuration, inorder to identify a wireless device ID. One or more parameters mayindicate one or more of a root index of a set of Zadoff-Chu (ZC)sequences, a cyclic shift (CS) index, a TDM/FDM pattern index, or anorthogonal cover code (OCC) sequence or index.

A base station may use one or more preamble sequences that may betransmitted together with the PUSCH data, for example, for a wirelessdevice ID identification. One or more preamble sequences may be designedto be reliable enough and to meet a detection requirement of a service,for example, URLLC. A preamble sequence may be uniquely allocated to awireless device, for example, for wireless devices configured with a GFradio resource pool. A base station may configure different GF radioresources for different sets of wireless devices such that the preamblesequences may be reused in different GF radio resources. The preamblesequences may be mutually orthogonal, for example orthogonality betweenZC root sequences with different cyclic shifts, which may providereliable detection performance. A wireless device may transmit one ormore preambles together with the data block in a first step and receivea response in a second step. The data from the data block may berepeated K times depending on a base station configuration. The one ormore preambles may not be repeated. The response from the base stationmay be, for example, a UL grant, or a dedicated ACK and/or NACK that maybe transmitted in the form of downlink control information (DCI).

A GF resource pool configuration may or may not be known to one or morewireless devices. A GF resource pool may be coordinated betweendifferent cells, for example, for interference coordination. GF resourcepools may be semi-statically configured by wireless device-specific RRCsignaling (e.g., if the GF resource pools are known to those wirelessdevices) or by non-wireless device-specific RRC signaling (e.g., viabroadcasting a system information block). The RRC signaling for GF radioresource configuration may include one or more parameters indicating oneor more of the following: periodicity and offset of a resource withrespect to SFN=0, time domain resource allocation, frequency domainresource allocation, wireless device-specific DMRS configuration, amodulation and coding scheme (MCS), a transport block size (TBS), numberof repetitions K, a hopping pattern, HARQ related parameters, or powercontrol related parameters. A wireless device may activate theconfigured grant transmission, that may be configured by the RRCsignaling, after or in response to receiving the RRC signaling withoutan additional signaling.

An L1 activation signaling may be used, for example, with RRC signaling,to configure and/or activate a configured grant (e.g., GF)configuration. RRC signaling may configure one or more parameters ofconfigured grant transmission to the wireless device. L1 activationsignaling may activate, or deactivate, the configured granttransmission. L1 activation signaling may be used to activate,configure, adjust, modify, and/or update one or more parametersassociated with configured grant transmission.

The L1 activation signaling may be transmitted via a PDCCH in the formof DCI, such as DCI used in UL semi-persistent scheduling (SPS). A basestation may assign a radio network temporary identifier (RNTI), for awireless device, along with configured grant configuration parameters inthe RRC signaling. Using the assigned RNTI, the wireless device maymonitor the PDCCH to receive L1 activation signaling that may be maskedby the RNTI. An uplink grant may be configured via RRC (e.g., forconfigured grant Type 1) or an uplink grant may be provided via PDCCHsignaling (e.g., for configured grant Type 2) which may be addressed toa CS-RNTI.

RRC configuration and/or reconfiguration of configured granttransmission without a dynamic UL grant may comprise one or more ofperiodicity of a resource or power control related parameters. L1activation signaling may provide one or more of the following parametersfor the configured grant resource: offset associated with theperiodicity with respect to a timing reference, time domain resourceallocation, frequency domain resource allocation, wirelessdevice-specific DMRS configuration, an MCS and/or TBS value, HARQrelated parameters, number of repetitions K, or a hopping pattern.

An MCS may be indicated by the wireless device within grant-free data. Anumber of MCS levels may be pre-configured by a base station, forexample, to avoid blind decoding of MCS indication. K bits may be usedto indicate MCS of grant-free data, where K may be as small as possible.The number of resource elements used to transmit MCS indication in aresource group may be semi-statically configured. In a configured grantoperation, there may be one common MCS for all wireless devices. Thecommon MCS may be predefined or determined by one or more devices. Theremay be a tradeoff between a spectrum efficiency and decodingreliability, such that the spectrum efficiency may be reduced, if a lowlevel of MCS is used, and the data transmission reliability mayincrease. A mapping rule, between multiple time and/or frequencyresources for UL grant-free transmission and MCSs, may be determinedbased on system requirements (e.g., NR requirements). A wireless devicemay select a MCS based on a DL measurement and associated time and/orfrequency resources to transmit UL data. The wireless device may selecta MCS, based on the channel status, and increase the resourceutilization.

A configured grant transmission may be activated in different ways, forexample, via RRC signaling or via L1 activation signaling, if a wirelessdevice is configured with a configured grant transmission. The need forL1 activation signaling may depend on service types, and the dynamicactivation (e.g., activation via L1 activation signaling) may not besupported or may be configurable based on service and/or trafficconsiderations.

A base station may determine whether to configure a wireless device withor without L1 activation signaling. The determination may be based on,for example, traffic pattern, latency requirements, and/or otherrequirements. By using L1 activation signaling, a wireless device maytransmit a data packet with configured time and/or frequency radioresource, for example, if the wireless device receives an L1 activationsignaling from the base station. A wireless device may start a ULtransmission with a configured GF radio resource at any moment, or in acertain time interval (which may be configured by RRC signaling orpre-defined) after the configuration is completed, for example, if theL1 activation signaling is not configured. A wireless device mayactivate the configured grant transmission after or in response toreceiving the RRC signaling configuring the configured granttransmission.

An activation type (e.g., via RRC signaling or via L1 activationsignaling) may be pre-configured. RRC signaling, transmitted from a basestation to a wireless device to configure a configured granttransmission, may comprise an indicator that may be used to indicatewhether the activation of the configured grant transmission requires anL1 activation signaling. If the indicator requires L1 activationsignaling, the wireless device may wait for an L1 activation signalingand activate the configured grant transmission after or in response toreceiving the L1 activation signaling. If L1 activation signaling isused, the wireless device may transmit an acknowledgement after or inresponse to receiving an L1 activation signaling to the base station toprovide an indication as to whether the wireless device correctlyreceives the L1 activation signaling.

The configured grant transmission may be activated after or in responseto the RRC signaling configuring the configured grant transmission, forexample, if the indicator indicates L1 activation signaling is notrequired. For the activation of configured grant transmission withoutthe L1 activation signaling, the wireless device may not determine whento start the configured grant transmission. The base station and thewireless device may predefine the start timing, for example, based on atime offset and the transmission time interval (TTI), such as asubframe, slot, or mini-slot, if the wireless device receives the RRCsignaling for the configured grant transmission configuration. The RRCconfiguration may comprise one or more parameters indicating the starttiming (e.g., in terms of a subframe, slot, or mini-slot).

RRC signaling may not contain an indicator as to whether the activationrequired a L1 activation signaling. A wireless device may implicitlyknow whether the configured grant transmission is activated by RRCsignaling or L1 activation signaling, for example, based on a format ofRRC configuration. For a configured grant transmission without L1activation signaling, the RRC signaling for configuring and activatingthe configured grant transmission may comprise one or more parametersfor the configured grant transmission. For a configured granttransmission activated by the L1 activation signaling, an RRC signalingmay comprise a different number of parameters that may be less than anumber of parameters in the RRC signaling activating the configuredgrant transmission. The absence of one or more parameters, and/or thenumber of parameters in the RRC signaling, may be an implicit indicatorfor a wireless device as to whether to activate the configured granttransmission, via RRC signaling or via L1 activation signaling.

The L1 activation signaling may comprise one or more parametersindicating one or more configured grant configurations, for example,start timing of configured grant transmission, configured grant time andfrequency radio resources, DMRS parameters, a modulation and codingscheme (MCS), a transport block size (TBS), number of repetitions K, ahopping pattern, or power control parameters. A downlink controlinformation (DCI) format used for the activation of the configured granttransmission may comprise one or more fields indicating a MCS for theconfigured grant transmission. The configured grant transmissionrequiring the L1 activation signaling may be configured with a RRCsignaling that may not comprise one or more parameters indicating theMCS for the configured grant transmission. The MCS information may becarried by a L1 signaling which may activate the configured granttransmission. A wireless device may activate the configured granttransmission after or in response to the RRC signaling, without waitingfor a L1 signaling, for example, if the wireless device receives a RRCsignaling comprising a MCS for a configured grant transmission.

The L1 activation signaling may be configured to control networkresource load and utilization, for example, if the service does notrequire high reliability and latency. For a delay sensitive service, theadditional activation signaling may cause additional delay and may leadto potential service interruption and/or unavailability for the periodof applying and requesting the activation. A base station may configurethe wireless device with a configured grant transmission such that theconfigured grant transmission may be activated after or in response tothe RRC signaling comprising a configured grant radio resourceconfiguration and transmission parameters.

The configured grant radio resource may become over-allocated, which mayresult in a waste of radio resources, for example, with few wirelessdevices. L1 signaling may be used to reconfigure the configured grantradio resource or one or more configured grant transmission parameters.By allowing L1 signaling-based reconfiguration, wireless devices mayperiodically monitor a downlink control channel to detect the L1signaling, scrambled by a RNTI, that may indicate whether the configuredgrant radio resources or parameters have changed. This monitoring mayincrease the power consumption of a wireless device, and the periodicityto check the downlink control signaling may be configurable. Theperiodicity may be configured to be short, such as every 1 minute orevery radio frame, for example, if a radio resource utilization may bemore important than a particular power consumption level. Theperiodicity may be configured to be long, such as every 1 hour, forexample, if a power consumption level may be important than a particularmonitoring periodicity. The periodicity to check downlink controlsignaling may be separated from the periodicity of configured granttransmission, for example, in order to shorten the latency. Theperiodicity of configured grant radio resource may be less than 1 ms,such as 0.125 ms, whereas the periodicity to check downlink controlsignaling may be greater, such as 1 minute or 1 hour. L1 deactivationsignaling may be used for all services in order to release resources asfast as possible, for example, for deactivating the activated configuredgrant operation.

For the configured grant transmission, a base station may support a Knumber of repetitions of the same transport block (TB) transmission overthe configured grant radio resource pool until one or more conditionsare met. A wireless device may continue the repetitions up to K timesfor the same TB until one or more of the following conditions is met: ifan UL grant (or HARQ ACK and/or NACK) is successfully received from thebase station before the number of repetitions reaches K, the number ofrepetitions for the TB reaches K, or other termination condition ofrepetitions may apply.

The number of repetitions, K, may be a configurable parameter that maybe wireless device-specific, and/or cell-specific. A unit of theK-repetition may comprise, for example, a mini-slot, a symbol, or anyother period. A base station may configure the number of this repetitionand the radio resource in advance, for example, via one or more RRCmessages. The base station may transmit L1 activation signalingcomprising a parameter indicating the number of repetitions K. The basestation may assume a set of initial transmission and the repetition asone amount of the transmission. The base station may not be limited toonly initial transmission or only repetition. The set of initialtransmission and its one or more repetitions may comprise an extendedTTI. The repetitions may not be necessarily contiguous in time. If therepetitions are contiguous in time, it may allow coherent combining. Ifthe repetitions are not contiguous in time, it may allow time diversity.

A base station may fail to detect a plurality of wireless devices' data,for example, if the configured grant transmission of the plurality ofwireless devices collides in the same GF radio resource pool. If twowireless devices retransmit the data without UL grants, the wirelessdevices may collide again. Hopping may be used to solve such a collisionproblem, for example, if radio resources are shared by multiple wirelessdevices. The hopping may randomize the collision relationship betweenwireless devices within a certain time interval that may avoidpersistent collision. The hopping may bring a diversity gain on thefrequency domain. A wireless device-specific hopping pattern may bepre-configured or may be indicated, for example, by RRC signaling or L1activation signaling. The wireless device-specific hopping pattern maybe generated based on a known wireless device-specific ID, for example,a wireless device-specific DMRS index and/or RNTI.

The hopping pattern may be determined from one or more factors, such asthe number of resource units (RUs), the maximum number of wirelessdevices sharing the same RU, the recently used RU index, the recenthopping index or the current slot index, the information indicatingrecently used sequence, hopping pattern, or hopping rule. A sequencesuch as referenced above may be a DMRS, a spreading sequence, or apreamble sequence that may be wireless device-specific.

The repetitions parameter K may be configured by one or more RRCmessages or L1 activation signaling. A wireless device configured withthe repetitions parameter K may transmit a transport block (TB) K times.The wireless device may transmit the TB K times with the same redundancyversion (RV) or the wireless device may transmit the TB K times withdifferent RVs between the repetitions. The RV determination for Krepetitions may comprise the initial transmission.

The RV determination may be fixed to a single value, fixed to apre-defined RV pattern comprising a plurality of RVs, configured by oneor more RRC messages with a single value, or configured by one or moreRRC messages with a RV pattern comprising a plurality of RVs, forexample, if the configured grant transmission is activated by one ormore RRC messages. The RV determination may be fixed to a single value,fixed to a pre-defined RV pattern comprising a plurality of RVs,configured by the one or more RRC messages with a single value,configured by one or more RRC messages with a RV pattern comprising aplurality of RVs, or configured by the L1 activation signaling with asingle value, or a RV pattern comprising a plurality of RVs, forexample, if the configured grant transmission is (fully or partially)configured by one or more RRC messages and activated by L1 activationsignaling.

A base station may switch between configured grant and dynamic grant ULtransmissions, for example, to balance resource utilization and delayand/or reliability requirements of associated services. The configuredgrant transmissions may be based on a semi-static resource configurationthat may be beneficial to reduce latency. Such a pre-defined resourceconfiguration may be difficult to satisfy all potential services orpacket sizes. The overhead may be large, and the packet size for aservice, such as URLLC, may be variable. If a wireless device's datapacket collides with other wireless device's packets in the configuredgrant transmission, a re-attempt to access configured grant radioresources may not achieve the service requirements and switching fromconfigured grant to dynamic grant UL transmissions may be beneficial.

The initial transmission on the pre-configured configured grant radioresources may include wireless device identification (ID), for example,to support the switching between configured grant and dynamic grant ULtransmissions. Wireless device identification may comprise explicitwireless device ID information (e.g., C-RNTI) or implicit wirelessdevice information such as a DMRS cyclic shift (assuming use of ZCsequences) specific signature. The wireless device may include bufferstatus reporting (BSR) with the initial data transmission, for example,to inform a base station of whether the wireless device has remainingdata to transmit. A base station may switch a type of scheduling for thewireless device from configured grant to dynamic grant UL transmissions,for example, if the base station successfully decodes data transmittedby a wireless device and determines (e.g. from a BSR report) that thewireless device has remaining data to transmit, and/or if the basestation fails to decode data transmitted by the wireless device butsuccessfully detects the wireless device ID from the uniquely assignedsequence (e.g., preamble and/or DMRS). The UL grant for subsequent datatransmissions may be with CRC scrambled by the wireless device's RNTI(which may be determined, for example, by explicit signaling in theinitial transmission or implicitly by the DMRS cyclic shift).

A termination condition, of one or more termination conditions, for theK-repetitions may be a reception of a DCI comprising an UL grant whichschedules an UL transmission and/or retransmission for the same TB. Abase station may assign dedicated resources for retransmission, forexample, in order to ensure that the TB is delivered within the latencybudget. Scheduling switching from configured grant to dynamic grantoperation may comprise such assignment of dedicated resources forretransmission. A wireless device may be required to link the receivedgrant with the transmitted TB, for example, to identify which TB is tobe retransmitted, such as if there are multiple ongoing transmissionprocesses at the wireless device. The wireless device and the basestation may have the same notion of TB (and/or RV) counting.

The TB counting for the configured grant operation may not be possible,for example, if a base station may not detect one or more TBs, such asdue to collisions. To make an association between a DCI with a TB, theremay be one or more options. The wireless device may directly associatethe DCI with a TB that is being transmitted, for example, if there is noother transmission process at the wireless device side. A wirelessdevice may determine that the DCI is for a particular TB by applying animplicit linkage that may assume only one TB is transmitted in onetransmission interval, for example, if there are at least two differentTBs. If the interval between detected wireless device transmission and agrant is fixed, the interval may determine which TB may beretransmitted. If the timing between a detected transmission and aretransmission grant is not preconfigured, an explicit indication of theretransmitted TB may be carried by DCI. If a wireless device detectsthat a grant for one TB overlaps with a transmission of another ongoingTB, the wireless device may assume precedence of the grant relative tothe grant-free retransmissions. If a grant is received for a new TB(e.g., for aperiodic CSI reporting) and if the grant overlaps with theconfigured grant transmissions, the configured grant transmissions maybe dropped in the resources. Additionally or alternatively, aprioritization rule whether to transmit a triggered report or configuredgrant data may be used, for example, depending on priority of theassociated services. For services such as URLLC services, the CSIreporting may be dropped.

A dedicated, pre-assigned channel may be used for early termination. Aphysical HARQ indicator channel (PHICH) may be used as an acknowledgeindicator. The PHICH for a wireless device may be determined based onthe physical resource block (PRB) and cyclic shift of the DMRScorresponding to the wireless device's PUSCH transmission. Similardesign principle may be used for a configured grant transmission. Theearly termination based on a PHICH-like channel may improve the controlchannel capacity and system capacity. If a base station has successfullyreceived a TB, the base station may obtain the corresponding informationabout the transmission of the TB, such as the wireless device ID, theresource used for carrying this transmission, and/or the DMRS used forthis transmission. The physical resources may be shared among multiplewireless devices that may have their own unique identifiers (e.g., DMRS)used in the configured grant radio resource pool. If the base stationhas successfully received a TB, a unique PHICH may be determined, forexample, even for configured grant transmission.

A sequence based signal may be used for early termination ofK-repetition. The sequence based signal may be transmitted, via one ormore pre-assigned channels, to inform the wireless device to terminatethe repetition of transmission. The signal may be transmitted if a basestation successfully decodes a TB. The wireless device may perform asimple signal detection for the presence or absence to decide whether tocontinue the repetitions.

A base station may switch from configured grant to dynamic grant ULtransmissions, for example, to improve a configured grant radio resourceshortage. One or more wireless devices having delay requirements thatare not strict (e.g., relative to URLLC requirements) may use theconfigured grant radio resource to transmit a data packet. The basestation may measure a level of congestion of the configured grant radioresource shared by a plurality of wireless devices based on statistics,for example, resource utilization, load, and/or a number of wirelessdevices sharing the configured grant radio resource and having set up athreshold policy to dynamically balance load or resource utilization ofthe configured grant radio resource. If the resource usage statistic ofthe configured grant radio resource exceeds a threshold, which may bepredefined, switching some wireless devices from the configured grantradio resource to the dynamic grant UL radio resource may providebenefits such as decreased resource collision.

A base station may switch from GF to GB UL transmissions. The basestation may switch to GB UL transmissions, for example, in order toimprove a GF radio resource shortage. One or more wireless devices withdelay requirements that are not strict (e.g., relative to URLLCrequirements) may use the GF radio resource to transmit one or more datapackets. A base station may measure a level of congestion of the GF ULradio resource shared by a plurality of wireless devices. The basestation may measure the level of congestion, for example, based onstatistics such as resource utilization, load, and/or a number ofwireless device sharing the GF UL radio resource. The base station mayset up a threshold policy, for example, to dynamically balance loadand/or resource utilization of the GF UL radio resource. It may bebeneficial to switch some wireless devices from the GF UL radio resourceto the GB UL radio resource, for example, if the resource usagestatistic of the GF UL radio resource exceeds a predefined threshold.Switching some wireless devices from the GF UL radio resource to the GBUL radio resource may result in decreasing resource collision.

A wireless device configured for operation with wireless resources(e.g., bandwidth parts (BWPs)) of a serving cell may be configured byhigher layers for the serving cell. The wireless device may beconfigured for a set of BWPs for receptions by the wireless device(e.g., DL BWP set) and/or or a set of BWPs for transmissions by thewireless device (e.g., UL BWP set). For a DL BWP, an UL BWP in a set ofDL BWPs, or an UL BWPs, the wireless device may be configured with atleast one of following for the serving cell: a subcarrier spacing for DLand/or UL provided by a higher layer parameter, a cyclic prefix for DLand/or UL provided by a higher layer parameter, a number of contiguousPRBs for DL and/or UL provided by a higher layer parameter, an offset ofthe first PRB for DL and/or UL in the number of contiguous PRBs relativeto the first PRB by a higher layer, and/or Q control resource sets(e.g., if the BWP is a DL BWP). Higher layer signaling may configure awireless device with Q control resource sets, for example, for eachserving cell. For a control resource set q, such that 0≤q<Q, theconfiguration may comprise one or more of following: a first OFDM symbolprovided by one or more higher layer parameters, a number of consecutiveOFDM symbols provided by one or more higher layer parameters, a set ofresource blocks provided by one or more higher layer parameters, aCCE-to-REG mapping provided by one or more higher layer parameters, aREG bundle size (e.g., for interleaved CCE-to-REG mapping provided byone or more higher layer parameters), and/or antenna portquasi-collocation provided by a higher layer parameter.

A control resource set may comprise a set of CCEs numbered from 0 toN_(CCE,q)−1, where N_(CCE,q) may be the number of CCEs in controlresource set q. Sets of PDCCH candidates that a wireless device monitorsmay be defined in terms of PDCCH wireless device-specific search spaces.A PDCCH wireless device-specific search space at CCE aggregation levelL∈{1, 2, 4, 8} may be defined by a set of PDCCH candidates for CCEaggregation level L. A wireless device may be configured (e.g., for aDCI format), per serving cell by one or more higher layer parameters,for a number of PDCCH candidates per CCE aggregation level L.

A wireless device may monitor (e.g., in non-DRX mode operation) one ormore PDCCH candidate in control resource set q according to aperiodicity of W_(PDCCH,q) symbols. The symbols may be configured by oneor more higher layer parameters for control resource set q. The carrierindicator field value may correspond to cif-InSchedulingCell, forexample, if a wireless device is configured with a higher layerparameter (e.g., cif-InSchedulingCell). For the serving cell on which awireless device may monitor one or more PDCCH candidate in a wirelessdevice-specific search space, the wireless device may monitor the one ormore PDCCH candidates without carrier indicator field (e.g., if thewireless device is not configured with a carrier indicator field). Forthe serving cell on which a wireless device may monitor one or morePDCCH candidates in a wireless device-specific search space, thewireless device may monitor the one or more PDCCH candidates withcarrier indicator field (e.g., if a wireless device is configured with acarrier indicator field). A wireless device may not monitor one or morePDCCH candidates on a secondary cell, for example, if the wirelessdevice is configured to monitor one or more PDCCH candidates withcarrier indicator field corresponding to that secondary cell in anotherserving cell. For the serving cell on which the wireless device maymonitor one or more PDCCH candidates, the wireless device may monitorthe one or more PDCCH candidates at least for the same serving cell.

A wireless device may receive PDCCH and/or PDSCH in a DL BWP accordingto a configured subcarrier spacing and CP length for the DL BWP. Awireless device may transmit PUCCH and/or PUSCH in an UL BWP accordingto a configured subcarrier spacing and CP length for the UL BWP.

A wireless device may be configured, by one or more higher layerparameters, for a DL BWP from a configured DL BWP set for DL receptions.A wireless device may be configured, by one or more higher layerparameters, for an UL BWP from a configured UL BWP set for ULtransmissions. A DL BWP index field value may indicate a DL BWP (such asfrom the configured DL BWP set) for DL receptions, for example, if theDL BWP index field is configured in a DCI format scheduling PDSCHreception to a wireless device. An UL-BWP index field value may indicatethe UL BWP (such as from the configured UL BWP set) for ULtransmissions, for example, if the UL-BWP index field is configured in aDCI format scheduling PUSCH transmission from a wireless device.

A wireless device may determine that the center frequency for the DL BWPis or should be the same as the center frequency for the UL BWP, such asfor TDD. The wireless device may not monitor PDCCH, for example, if thewireless device performs measurements over a bandwidth that is notwithin the DL BWP for the wireless device.

A wireless device may identify the bandwidth and/or frequency of aninitial active DL BWP, such as for an initial active DL BWP. Thewireless device may identify the bandwidth and/or frequency after or inresponse to receiving the NR-PBCH. A bandwidth of an initial active DLBWP may be confined within the wireless device minimum bandwidth for thegiven frequency band. The bandwidth may be indicated in PBCH, such asfor flexible DL information scheduling. Some bandwidth candidates may bepredefined. A number of bits (e.g., x bits) may be used for a bandwidthindication.

A frequency location of an initial active DL BWP may be derived from thebandwidth and SS block (e.g., a center frequency of the initial activeDL BWP). The edge of the SS block PRB and data PRB boundary may not bealigned. An SS block may have a frequency offset, for example, if theedge of the SS block PRB and data PRB are not aligned. Predefining thefrequency location of an SS block and an initial active DL BWP mayreduce the PBCH payload size such that additional bits may not be neededfor an indication of a frequency location of an initial active DL BWP.The bandwidth and frequency location may be informed in RMSI, forexample, for the paired UL BWP.

A base station may configure a set of BWPs for a wireless device by RRCsignaling. The wireless device may transmit or receive in an active BWPfrom the configured BWPs in a given time instance. An activation and/ora deactivation of DL bandwidth part may be based on a timer for awireless device. The wireless device may switch its active DL bandwidthpart to a default DL bandwidth part, for example, if a timer expires. Ifthe wireless device has not received scheduling DCI for a time period(e.g., X ms, or after expiry of a timer), the wireless device may switchto the default DL BWP.

A new timer (e.g., BWPDeactivationTimer) may be defined to deactivatethe original BWP and/or switch to the default BWP. The new timer (e.g.,BWPDeactivationTimer) may be started if the original BWP is activated bythe activation and/or deactivation DCI. If PDCCH on the original BWP isreceived, a wireless device may restart the timer (e.g.,BWPDeactivationTimer) associated with the original BWP. If the timer(e.g., BWPDeactivationTimer) expires, a wireless device may deactivatethe original BWP, switch to the default BWP, stop the timer for theoriginal BWP, and/or flush (or not flush) all HARQ buffers associatedwith the original BWP.

A base station and a wireless device may have a different understandingof the starting of the timer, for example, if the wireless device missesone or more scheduling grants. The wireless device may be triggered toswitch to the default BWP, but the base station may schedule thewireless device in the previous active BWP. The base station mayrestrict the location of the CORESET of BWP2 to be within BWP1 (e.g.,the narrow band BWP1 may be the default BWP), for example, if thedefault BWP is nested within other BWPs. The wireless device may receivean indication (e.g., CORESET) and switch back to BWP2, for example, ifthe wireless device previously mistakenly switched to the default BWP.

Restricting the location of the indication (e.g., CORESET) may not solvea miss switching problem, for example, if the default BWP and the otherBWPs are not overlapped in frequency domain. The base station maymaintain a timer for a wireless device. If the timer expires (e.g., ifthere is no data scheduled for the wireless device for a time periodsuch as Y ms), and/or if the base station has not received feedback fromthe wireless device for a time period (such as Y′ ms), the wirelessdevice may switch to the default BWP. The wireless device may switch tothe default BWP to send a paging signal and/or to re-schedule thewireless device in the default BWP.

A base station may not fix the default bandwidth part to be the same asan initial active bandwidth part. The initial active DL BWP may be theSS block bandwidth which is common to wireless devices in the cell. Thetraffic load may be very heavy, for example, if many wireless devicesfall back to a small bandwidth for data transmission. Configuring thewireless devices with different default BWPs may help to balance theload in the system bandwidth.

There may be no initial active BWP on an SCell, for example, if theinitial access is performed on the PCell. An DL BWP and/or UL BWP thatis initially activated based on the SCell being activated may beconfigured or reconfigured by RRC signaling. The default BWP of theSCell may also be configured and/or reconfigured by RRC signaling. Thedefault BWP may be configured or reconfigured by the RRC signaling,and/or the default BWP may be one of the configured BWPs of the wirelessdevice, which may provide a unified design for both PCell and SCell.

The base station may configure a wireless device-specific default DL BWPother than an initial active BWP. The base station may configure thewireless device-specific default DL BWP, for example, after RRCconnection, which may be performed for the purpose of load balancing.The default BWP may support connected mode operations other thanoperations supported by initial active BWP. Other connected modeoperations may comprise, for example, fall back and/or connected modepaging. The default BWP may comprise a common search space, such as atleast the search space needed for monitoring the pre-emptionindications. The default DL and UL BWPs may be independently configuredto the wireless device, such as for FDD.

The initial active DL BWP and/or UL BWP may be set as default DL BWPand/or UL BWP, respectively. A wireless device may return to default DLBWP and/or UL BWP. For example, if a wireless device does not receivecontrol for a long time (e.g., based on a timer expiration or a timeduration reaching a threshold), the wireless device may fall back to adefault BWP (e.g., default DL BWP and/or default UL BWP).

A base station may configure a wireless device with multiple BWPs. Themultiple BWPs may share at least one CORESET including a default BWP.CORESET for RMSI may be shared for all configured BWPs. The wirelessdevice may receive control information via the common CORESET, forexample, without going back to another BWP or a default BWP. The commonCORESET may schedule data within only a default BWP, which may minimizethe ambiguity of resource allocation, for example, if a frequency regionof a default BWP may belong to all or more than one of the configuredBWPs.

A semi-static pattern of BWP switching to default BWP may be performed,for example, if the configured BWP is associated with a differentnumerology from a default BWP. Switching to a default BWP may beperformed, for example, to check RMSI at least periodically. Switchingto a default BWP may be necessary particularly if BWPs use differentnumerologies.

Reconfiguration of a default BWP from an initial BWP may be performed,such as for RRC connected wireless devices. A default BWP may be thesame as an initial BWP, such as for RRC IDLE wireless devices.Additionally or alternatively, a wireless device (e.g., RRC IDLEwireless device) may fall back to an initial BWP regardless of a defaultBWP. If a wireless device performs a measurement based on SS block,reconfiguration of a default BWP outside of an initial BWP may becomevery inefficient, for example, due to frequent measurement gaps. If adefault BWP is reconfigured to outside of an initial BWP, the followingconditions may be satisfied: a wireless device may be in a CONNECTEDmode, and/or a wireless device may not be configured with an SS blockbased measurement for both serving cell and neighbor cells.

A DL BWP other than the initial active DL BWP may be configured as thedefault DL BWP for a wireless device. Reconfiguring the default DL BWPmay be performed based on load balancing and/or different numerologiesused for an active DL BWP and an initial active DL BWP. A default BWP ona PCell may be an initial active DL BWP for a transmission of RMSI. Thetransmission of RMSI may comprise one or more of an RMSI CORESET with aCSS, and/or a wireless device-specific search space (e.g., USS). Theinitial active BWP and/or default BWP may remain an active BWP for auser after a wireless device becomes RRC connected.

Downlink and uplink BWPs may be independently activated, such as for apaired spectrum. Downlink and uplink bandwidth parts may be jointlyactivated, such as for an unpaired spectrum. In bandwidth adaptation(e.g., where the bandwidth of the active downlink BWP may be changed), ajoint activation of a new downlink BWP and a new uplink BWP may beperformed (e.g., for an unpaired spectrum). A new DL/UL BWP pair may beactivated such that the bandwidth of the uplink BWPs may be the same(e.g., there may not be a change of an uplink BWP).

There may be an association of DL BWP and UL BWP in RRC configuration.For example, a wireless device may not retune the center frequency of achannel bandwidth (BW) between DL and UL, such as for TDD. If the RF isshared between DL and UL (e.g., in TDD), a wireless device may notretune the RF BW for every alternating DL-to-UL and UL-to-DL switching.

Applying an association between a DL BWP and an UL BWP may enable anactivation and/or deactivation command to switch both DL and UL BWPs.Such switching may comprise switching a DL BWP together with switchingan UL BWP. If an association is not applied between a DL BWP and an ULBWP, separate BWP switching commands may be necessary.

A DL BWP and an UL BWP may be configured separately for the wirelessdevice. Pairing of the DL BWP and the UL BWP may impose constraints onthe configured BWPs (e.g., the paired DL BWP and UL BWP may be activatedsimultaneously or near simultaneously such as within a threshold timeperiod). A base station may indicate a DL BWP and an UL BWP to awireless device for activation, for example, in a FDD system. A basestation may indicate to a wireless device a DL BWP and an UL BWP withthe same center frequency for activation, for example, in a TDD system.No pairing and/or association of the DL BWP and UL BWP may be mandatory,even for TDD system, for example, if the activation and/or deactivationof the BWP for the wireless device is instructed by the base station.Pairing and/or association of the DL BWP and UL BWP may be determined bya base station.

An association between a DL carrier and an UL carrier within a servingcell may be performed by carrier association. A wireless device may notbe expected to retune the center frequency of a channel BW between DLand UL, such as for a TDD system. An association between a DL BWP and anUL BWP may be required for a wireless device. An association may beperformed by grouping DL BWP configurations with same center frequencyas one set of DL BWPs and grouping UL BWP configurations with samecenter frequency as one set of UL BWPs. The set of DL BWPs may beassociated with the set of UL BWPs sharing the same center frequency.There may be no association between a DL BWP and an UL BWP, for example,if the association between a DL carrier and an UL carrier within aserving cell may performed by carrier association, such as for an FDDserving cell.

A wireless device may identify a BWP identity from a DCI, which maysimplify an indication process. The total number of bits for a BWPidentity may depend on the number of bits that may be used within ascheduling DCI (and/or a switching DCI), and/or the wireless deviceminimum BW. The number of BWPs may be determined based on the wirelessdevice supported minimum BW and/or the network maximum BW. The maximumnumber of BWPs may be determined based on the network maximum BW and/orthe wireless device minimum BW. For example, if 400 MHz is the networkmaximum BW and 50 MHz is the wireless device minimum BW, 8 BWPs may beconfigured to the wireless device such that 3 bits may be requiredwithin the DCI to indicate the BWP. Such a split of the network BW(e.g., depending on the wireless device minimum BW) may be useful forcreating one or more default BWPs from the network side by distributingwireless devices across the entire network BW (e.g., for load balancingpurposes).

At least two DL and two UL BWPs may be supported by a wireless devicefor a BWP adaption. The total number of BWPs supported by a wirelessdevice may be given by 2≤number of DL/UL BWP≤floor (network maximumBW/wireless device minimum DL/UL BW), where floor(x) may be a floorfunction that returns the greatest integer being less than or equal tox. For example, a maximum number of configured BWPs may be four for DLand UL, respectively, or a maximum number of configured BWPs for UL maybe two. Any other number of BWPs, for example, greater than or equal to2 and less than or equal to a floor, may be supported by a wirelessdevice.

Different sets of BWPs may be configured for different DCI formatsand/or scheduling types, respectively. BWPs may be configured fornon-slot-based scheduling (e.g., for larger BWPs) or for slot-basedscheduling (e.g., for smaller BWPs). If different DCI formats aredefined for slot-based scheduling and non-slot-based scheduling,different BWPs may be configured for different DCI formats. DifferentBWP configurations may provide flexibility between different schedulingtypes without increasing DCI overhead. A 2-bit field may be used toindicate a BWP among four BWPs for a DCI format. For example, four DLBWPs or two or four UL BWPs may be configured for each DCI format. Thesame or different BWPs may be configured for different DCI formats.

A required maximum number of configured BWPs (which may exclude theinitial BWP) may depend on the flexibility needed for a BWPfunctionality. It may be sufficient to be able to configure one DL BWPand one UL BWP (or a single DL/UL BWP pair for an unpaired spectrum),which may correspond to minimal support of bandlimited devices. Theremay be a need to configure at least two DL BWPs and at least a singleuplink BWP for a paired spectrum (or two DL/UL BWP pairs for an unpairedspectrum), such as to support bandwidth adaptation. There may be a needto configure one or more DL (or UL) BWPs that jointly cover differentparts of the downlink (or uplink) carrier, such as to support dynamicload balancing between different parts of the spectrum. Two BWPs may besufficient, for example, for dynamic load balancing. In addition to thetwo bandwidth parts, two other bandwidth parts may be needed, such asfor bandwidth adaptation. A maximum number of configured BWPs may befour DL BWPs and two UL BWPs for a paired spectrum. A maximum number ofconfigured BWPs may be four DL/UL BWP pairs for an unpaired spectrum.

A wireless device may monitor for RMSI and broadcasted OSI, which may betransmitted by a base station within a common search space (CSS) on thePCell. RACH response and paging control monitoring on the PCell may betransmitted within the CSS. A wireless device may not monitor the commonsearch space, for example, if the wireless device is allowed to be on anactive BWP configured with a wireless device-specific search space (USSSor USS).

At least one of configured DL bandwidth parts may comprise at least oneCORESET with a CSS type, such as for a PCell. To monitor RMSI andbroadcast OSI, the wireless device may periodically switch to the BWPcontaining the CSS. The wireless device may periodically switch to theBWP containing the CSS for RACH response and paging control monitoringon the PCell.

BWP switching to monitor the CSS may result in increasing overhead, forexample, if the BWP switching occurs frequently. The overhead due to theCSS monitoring may depend on an overlapping in frequency between any twoBWPs. In a nested BWP configuration (e.g., where one BWP may be a subsetof another BWP), the same CORESET configuration may be used across theBWPs. A default BWP may comprise the CSS, and another BWP may comprisethe CSS, for example, if the default BWP is a subset of another BWP. TheBWPs may be partially overlapping. A CSS may be across a first BWP and asecond BWP, for example, if the overlapping region is sufficient. Twonon-overlapping BWP configurations may exist.

There may be one or more benefits from configuring the same CORESETcontaining the CSS across BWPs. For example, the RMSI and broadcast OSImonitoring may be performed without necessitating BWP switching, RACHresponse and paging control monitoring on the PCell may be performedwithout switching, and/or robustness for BWP switching may improve. Abase station and a wireless device may be out-of-sync as to which BWP iscurrently active and the DL control channel may still work, for example,if CORESET configuration is the same across BWPs. One or moreconstraints on BWP configuration may be acceptable. A BWP may providepower saving, such that various configurations, including a nestedconfiguration, may be very versatile for different applications. For BWPconfigurations that are non-overlapping in frequency, a wireless devicemay not have specific requirements to monitor RMSI and broadcast OSI inthe CSS.

Group-common search space (GCSS) may be supported (e.g., in NR). TheGCSS may be used in addition to or as an alternative to CSS for certaininformation. A base station may configure GCSS within a BWP for awireless device. Information such as RACH response and paging controlmay be transmitted on GCSS. The wireless device may monitor GCSS, forexample, instead of switching to the BWP containing the CSS for suchinformation. A base station may transmit information on GCSS, forexample, for a pre-emption indication and other group-based commands ona serving cell. A wireless device may monitor the GCSS for theinformation, including for example, for the SCell which may not haveCSS.

A CORESET may be configured without using a BWP. The CORESET may beconfigured based on a BWP, which may reduce signaling overhead. A firstCORESET for a wireless device during an initial access may be configuredbased on a default BWP. A CORESET for monitoring PDCCH for RAR andpaging may be configured based on a DL BWP. The CORESET for monitoringgroup common (GC)-PDCCH for SFI may be configured based on a DL BWP. TheCORESET for monitoring GC-DCI for a pre-emption indication may beconfigured based on a DL BWP. A BWP index may be indicated in theCORESET configuration. A default BWP index may not be indicated in theCORESET configuration.

A contention-based random access (CBRA) RACH procedure may be supportedvia an initial active DL BWP and/or an initial active UL BWP, forexample, if the wireless device identity is unknown to the base station.The contention-free random access (CFRA) RACH procedure may be supportedvia the USS configured in an active DL BWP for the wireless device. Anadditional CSS for RACH purposes may not need to be configured per BWP,such as for the CFRA RACH procedure supported via the USS configured inan active DL BWP for the wireless device. Idle mode paging may besupported via an initial active DL BWP. Connected mode paging may besupported via a default BWP. No additional configurations for the BWPfor paging purposes may be needed for paging. A configured BWP (e.g., ona serving cell) may have the CSS configured for monitoring pre-emptionindications for a pre-emption.

A group-common search space may be associated with at least one CORESETconfigured for the same DL BWP (e.g., for a configured DL BWP). Thewireless device may or may not autonomously switch to a default BWP(e.g., where a group-common search space may be available) to monitorfor a DCI, for example, depending on the monitoring periodicity ofdifferent group-common control information types. A group-common searchspace may be configured in the same CORESET, for example, if there is atleast one CORESET configured on a DL BWP.

A center frequency of an activated DL BWP may or may not be changed. Ifthe center frequency of the activated DL BWP and the deactivated DL BWPis not aligned, the active UL BWP may be switched implicitly (e.g., forTDD).

BWPs with different numerologies may be overlapped. Rate matching forCSI-RS and/or SRS of another BWP in the overlapped region may beperformed, which may achieve dynamic resource allocation of differentnumerologies in a FDM and/or a TDM manner. For a CSI measurement withinone BWP, if the CSI-RS and/or SRS collides with data and/or an RS inanother BWP, the collision region in another BWP may be rate matched.CSI information over the two or more BWPs may be determined by a basestation based on wireless device reporting. Dynamic resource allocationwith different numerologies in a FDM manner may be achieved by basestation scheduling.

PUCCH resources may be configured in a configured UL BWP, in a defaultUL BWP, and/or in both a configured UL BWP and a default UL BWP. If thePUCCH resources are configured in the default UL BWP, a wireless devicemay retune to the default UL BWP for transmitting an SR. The PUCCHresources may be configured per a default BWP or per a BWP other thanthe default BWP. The wireless device may transmit an SR in the currentactive BWP without retuning. If a configured SCell is activated for awireless device, a DL BWP may be associated with an UL BWP at least forthe purpose of PUCCH transmission, and/or a default DL BWP may beactivated. If the wireless device is configured for UL transmission inthe same serving cell, a default UL BWP may be activated.

At least one of configured DL BWPs may comprise one CORESET with commonsearch space (CSS), for example, at least in a primary componentcarrier. The CSS may be needed at least for RACH response (e.g., a msg2)and/or a pre-emption indication. One or more of configured DL bandwidthparts for a PCell may comprise a CORESET with the CSS type for RMSIand/or OSI, for example, if there is no periodic gap for RACH responsemonitoring on the PCell. A configured DL bandwidth part for a PCell maycomprise one CORESET with the CSS type for RACH response and pagingcontrol for a system information update. A configured DL bandwidth partfor a serving cell may comprise a CORESET with the CSS type for apre-emption indication and/or other group-based commands. One or more ofconfigured DL bandwidth parts for a PCell may comprise a CORESET with aCSS type for RMSI, OSI, and/or RACH response and paging control for asystem information update, for example, if a periodic gap for RAHCresponse monitoring is present on the PCell. A configured DL bandwidthpart for a serving cell may comprise a CORESET with a CSS type for apre-emption indication and/or other group-based commands.

BWPs may be configured with respect to common reference point (e.g., PRB0) on a component carrier. The BWPs may be configured using TYPE1 RA asa set of contiguous PRBs, with PRB granularity for the START and LENGTH.The minimum length may be determined by the minimum supported size of aCORESET. A CSS may be configured on a non-initial BWP, such as for RARand paging.

To monitor common channel or group common channel for a connectedwireless device (e.g., RRC CONNECTED UE), an initial DL BWP may comprisea control channel for RMSI, OSI, and/or paging. The wireless device mayswitch a BWP to monitor such a control channel. A configured DL BWP maycomprise a control channel (e.g., for a Msg2). A configured DL BWP maycomprise a control channel for a SFI. A configured DL BWP may comprise apre-emption indication and/or other group common indicators such as forpower control.

A DCI may explicitly indicate activation and/or deactivation of a BWP. ADCI without data assignment may comprise an indication to activateand/or deactivate BWP. A wireless device may receive a first indicationvia a first DCI to activate and/or deactivate a BWP. A second DCI with adata assignment may be transmitted by the base station, for example, fora wireless device to start receiving data. The wireless device mayreceive the first DCI in a target CORESET within a target BWP. A basestation scheduler may make conservative scheduling decisions, forexample, until the base station receives CSI feedback.

A DCI without scheduling for active BWP switching may be transmitted,for example, to measure the CSI before scheduling. A DCI with schedulingfor active BWP switching may comprise setting the resource allocationfield to zero, such that no data may be scheduled. Other fields in theDCI may comprise one or more CSI and/or SRS request fields.

Single scheduling a DCI to trigger active BWP switching may providedynamic BWP adaptation for wireless device power saving during activestate. Wireless device power saving during active state may occur for anON duration, and/or if an inactivity timer is running and/or if C-DRX isconfigured. A wireless device may consume a significant amount of powermonitoring PDCCH, without decoding any grant, for example if a C-DRX isenabled. To reduce the power consumption during PDCCH monitoring, twoBWPs may be configured: a narrower BWP for PDCCH monitoring, and a widerBWP for scheduled data. The wireless device may switch back-and-forthbetween the narrower BWP and the wider BWP, depending on the burstinessof the traffic. The wireless device may revisit a BWP that it haspreviously used. Combining a BWP switching indication and a schedulinggrant may provide an advantage of low latency and/or reduced signalingoverhead for BWP switching.

An SCell activation and/or deactivation may or may not trigger acorresponding action for its configured BWP. A dedicated BWP activationand/or deactivation DCI may impact a DCI format. A scheduling DCI with adummy grant may be used. The dummy grant may be constructed byinvalidating one or some of the fields, such as the resource allocationfield. A fallback scheduling DCI format (which may contain a smallerpayload) may be used, which may improve the robustness for BWP DCIsignaling without incurring extra work by introducing a new DCI format.

A DCI with data assignment may comprise an indication to activate and/ordeactivate a BWP along with a data assignment. A wireless device mayreceive a combined data allocation and BWP activation and/ordeactivation message. A DCI format may comprise a field to indicate BWPactivation and/or deactivation and/or a field indicating an UL grantand/or a DL grant. The wireless device may start receiving data with asingle DCI, such as the DCI format described above. The DCI may indicateone or more target resources of a target BWP. A base station schedulermay have insufficient information about the CSI in the target BW and maymake conservative scheduling decisions.

The DCI may be transmitted on a current active BWP, and schedulinginformation may be for a new BWP, for example, for the DCI with dataassignment. There may be a single active BWP. There may be one DCI in aslot for scheduling the current BWP or scheduling another BWP. The sameCORESET may be used for the DCI scheduling of the current BWP and theDCI scheduling of another BWP. The DCI payload size for the DCIscheduling current BWP and the scheduling DCI for BWP switching may bethe same, which may reduce the number of blind decoding attempts.

A BWP group may be configured by a base station, in which a numerologyin one group may be the same, which may support using the scheduling DCIfor BWP switching. The BWP switching for the BWP group may beconfigured, such that BIF may be present in the CORESETs for one or moreBWPs in the group. Scheduling DCI for BWP switching may be configuredper BWP group, in which an active BWP in the group may be switched toany other BWP in the group.

A DCI comprising a scheduling assignment and/or grant may not comprisean active-BWP indicator. A scheduling DCI may switch a wireless devicesactive BWP to the transmission direction for which the scheduling isvalid (e.g., for a paired spectrum). A scheduling DCI may switch thewireless devices active DL/UL BWP pair regardless of the transmissiondirection for which the scheduling is valid (e.g., for an unpairedspectrum). A downlink scheduling assignment and/or grant with noassignment may occur, which may allow for a switching of an active BWPwithout scheduling downlink and/or uplink transmissions.

A timer-based activation and/or deactivation BWP may be supported. Atimer for activation and/or deactivation of DL BWP may reduce signalingoverhead and may allow wireless device power savings. The activationand/or deactivation of a DL BWP may be based on an inactivity timer,which may be referred to as a BWP inactive (or inactivity) timer. Awireless device may start and/or reset a timer upon reception of a DCI.The timer may expire, for example, if the wireless device is notscheduled for the duration of the timer. The wireless device mayactivate and/or deactivate the appropriate BWP based on the expiry ofthe timer. The wireless device may, for example, activate the defaultBWP and/or deactivate the source BWP.

A BWP inactive timer may be beneficial for power saving for a wirelessdevice. A wireless device may reduce power, for example, by switching toa default BWP with a smaller bandwidth. A wireless device may use a BWPinactive timer, for example, for a fallback if missing a DCI basedactivation and/or deactivation signaling, such as by switching from oneBWP to another BWP. Triggering conditions of the BWP inactive timer mayfollow triggering conditions for the DRX timer in LTE or any othersystem. An on-duration of the BWP inactive timer may be configuredand/or the timer may start, for example, if a wireless device-specificPDCCH is successfully decoded indicating a new transmission during theon-duration. The timer may restart, for example, if a wirelessdevice-specific PDCCH is successfully decoded indicating a newtransmission. The timer may stop, for example, if the wireless device isscheduled to switch to the default DL BWP. The BWP inactive timer maystart, for example, if the wireless device switches to a new DL BWP. Thetimer may restart, for example, if a wireless device-specific PDCCH issuccessfully decoded, wherein the wireless device-specific PDCCH may beassociated with a new transmission, a retransmission, SPS activationand/or deactivation, or another purpose.

A wireless device may switch to a default BWP, for example, if thewireless device does not receive any control and/or data from thenetwork during the running of the BWP inactive timer. The timer may bereset, for example, upon reception of any control and/or data. The timermay be triggered, for example, if wireless device receives a DCI toswitch its active DL BWP from the default BWP to another BWP. The timermay be reset, for example, if a wireless device receives a DCI toschedule PDSCH(s) in the BWP other than the default BWP.

A DL BWP inactive timer may be defined separately from a UL BWP inactivetimer. Timers for the DL BWP and UL BWP may be set independently and/orjointly. For the separate timers (e.g., if there is DL data and UL timerexpires), UL BWP may not be deactivated since PUCCH configuration may beaffected if both DL BWP and UL BWP are activated. For the uplink, ifthere is UL feedback signal related to DL transmission, the timer may bereset. The UL timer may not be set if there is DL data. If there is ULdata and the DL timer expires, there may be no issue if the DL BWP isdeactivated since UL grant is transmitted in the default DL BWP. A BWPinactivity-timer may allow fallback to default BWP on a PCell and/orSCell.

A timer-based activation and/or deactivation of BWP may be similar to awireless device DRX timer. There may not be a separate inactivity timerfor BWP activation and/or deactivation for the wireless device DRXtimer. A wireless device DRX inactivity timer may trigger BWP activationand/or deactivation. There may be separate inactivity timers for BWPactivation and/or deactivation for the wireless device DRX timer. Forexample, the DRX timers may be defined in a MAC layer, and the BWP timermay be defined in a physical layer. A wireless device may stay in awider BWP for as long as the inactivity timer is running, for example,if the same DRX inactivity timer is used for BWP activation and/ordeactivation. The DRX inactivity timer may be set to a large value of100-200 milliseconds for a C-DRX cycle of 320 milliseconds, which may belarger than the ON duration (e.g., 10 milliseconds). Setting the DRXinactivity timer in the above manner may provide power savings, forexample, based on a narrower BWP not being achievable. To realizewireless device power saving promised by BWP switching, a new timer maybe defined and it may be configured to be smaller than the DRXinactivity timer. From the point of view of DRX operation, BWP switchingmay allow wireless device to operate at different power levels duringthe active state, effectively providing intermediate operating pointsbetween the ON and OFF states.

With a DCI explicit activation and/or deactivation of BWP, a wirelessdevice and a base station may not be synchronized with respect to whichBWP is activated and/or deactivated. The base station scheduler may nothave CSI information related to a target BWP for channel-sensitivescheduling. The base station may be limited to conservative schedulingfor one or more first several scheduling occasions. The base station mayrely on periodic or aperiodic CSI-RS and associated CQI report(s) toperform channel-sensitive scheduling. Relying on periodic or aperiodicCSI-RS and associated CQI report(s) may delay channel-sensitivescheduling and/or lead to signaling overhead, such as if aperiodic CQIis requested. To mitigate a delay in acquiring synchronization andchannel state information, a wireless device may transmit anacknowledgement upon receiving an activation and/or deactivation of aBWP. A CSI report based on the provided CSI-RS resource may betransmitted after activation of a BWP and may be used as acknowledgmentof activation and/or deactivation.

A base station may provide a sounding reference signal for a target BWPafter a wireless device tunes to a new BWP. The wireless device mayreport the CSI, which may be used as an acknowledgement by the basestation to confirm that the wireless device receives an explicit DCIcommand and activates and/or deactivates the appropriate BWPs. For anexplicit activation and/or deactivation via DCI with data assignment, afirst data assignment may be carried out without a CSI for the targetBWP.

A guard period may be defined to take RF retuning and related operationsinto account. A wireless device may neither transmit nor receive signalsin the guard period. A base station may need to know the length of theguard period. For example, the length of the guard period may bereported to the base station as a wireless device capability. The lengthof the guard period may be based on the numerologies of the BWPs and thelength of the slot. The length of the guard period for RF retuning maybe reported as a wireless device capability. The wireless device mayreport the guard period as an absolute time and/or in symbols.

The base station may maintain the time domain position of guard periodin alignment between the base station and the wireless device, forexample, if the base station knows the length of the guard period. Theguard period for RF retuning may be predefined for time patterntriggered BWP switching. The BWP switching and/or guard period may betriggered by DCI and/or a timer. For BWP switching following a timepattern, the position of the guard period may be defined. The guardperiod may not affect the symbols carrying CSS, for example, if thewireless device is configured to switch periodically to a default BWPfor CSS monitoring.

A single DCI may switch the wireless device's active BWP from one toanother within a given serving cell. The active BWP may be switched to asecond BWP of the same link direction, for example an UL BWP or a DLBWP. A separate field may be used in the scheduling DCI to indicate theindex of the BWP for activation such that wireless device may determinethe current DL/UL BWP according to a detected DL/UL grant withoutrequiring any other control information. The multiple scheduling DCIstransmitted in this duration may comprise the indication to the sameBWP, for example, if the BWP change does not happen during a certaintime duration. During the transit time wherein potential ambiguity mayhappen, base station may send scheduling grants in the current BWP ortogether in the other BWPs containing the same target BWP index, suchthat wireless device may obtain the target BWP index by detecting thescheduling DCI in either one of the BWPs. The duplicated scheduling DCImay be transmitted an arbitrary number (e.g., K) times. A wirelessdevice may switch to the target BWP and start to receive or transmit(UL) in the target BWP according to the BWP indication field, forexample, if the wireless device receives one of the K timestransmissions.

Switching between BWPs may introduce time gaps, for example, if wirelessdevice is unable to receive one or more messages due to re-tuning.Breaks of several time slots may severely affect the TCP ramp up as thewireless device may not be able to transmit and receive during thoseslots, affecting obtained RTT and data rate. A break in reception maymake wireless device out of reach from network point of view reducingnetwork interest to utilize short inactivity timer. If BWP switchingtakes significant time and a wireless device requires new referencesymbols to update AGC, channel estimation, etc., active BWP switchingmay not be adopted in the wireless device. In some configurations, BWPswitching may be performed where the BWP center frequency remains thesame if switching between BWPs.

A frequency location of a wireless device's RF bandwidth may beindicated by base station. The RF bandwidth of the wireless device maybe smaller than the carrier bandwidth for considering the wirelessdevice RF bandwidth capability. The supported RF bandwidth for awireless device is usually a set of discrete values (e.g., 10 MHz, 20MHz, 50 MHz, etc.). For energy saving purpose, the wireless device RFbandwidth may be determined as the minimum available bandwidthsupporting the bandwidth of the BWP. The granularity of BWP bandwidthmay be PRB level, which may be decoupled with wireless device RFbandwidth. As a result, the wireless device RF bandwidth may be largerthan the BWP bandwidth. The wireless device may receive signals outsidethe carrier bandwidth, especially if the configured BWP is configurednear the edge of the carrier bandwidth. Inter-system interference or theinterference from an adjacent cell outside the carrier bandwidth mayaffect the receiving performance of the BWP. To keep the wireless deviceRF bandwidth in the carrier bandwidth, the frequency location of thewireless device RF bandwidth may be indicated by base station.

A gap duration may be determined based on a measurement duration and aretuning gap. The retuning gap may vary. If a wireless device does notneed to switch its center, the retuning may be relatively short, such as20 μs. A wireless device may indicate the necessary retuning gap for ameasurement configuration, for example, if the network may not knowwhether the wireless device needs to switch its center or not to performmeasurement. The returning gap may depend on the current active BWP thatmay be dynamically switched via switching mechanism. Wireless devicesmay need to indicate the returning gap dynamically.

The measurement gap may be indirectly created, for example, if thenetwork may configure a certain measurement gap. The measurement gap maycomprise the smallest retuning latency. The smallest returning latencymay be determined, for example, if a small retuning gap may be utilizedand/or if both measurement bandwidth and active BWP is included withinthe wireless device maximum RF capability and the center frequency ofthe current active BWP may be not changed. The wireless device may skipreceiving and/or transmitting, for example, if a wireless device needsmore gap than the configured.

A different measurement gap and retuning gap may be utilized for RRM andCSI. For CSI measurement, if periodic CSI measurement outside of activeBWP may be configured, a wireless device may need to perform itsmeasurement periodically per measurement configuration. For RRM, it maybe up to wireless device implementation where to perform the measurementas long as it satisfies the measurement requirements. The worst caseretuning latency for a measurement may be used. As the retuning latencymay be different between intra-band and inter-band retuning, separatemeasurement gap configurations between intra-band and inter-bandmeasurement may be considered.

A respective DCI format may comprise an explicit identifier todistinguish them, for example, for multiple DCI formats with the sameDCI size of a same RNTI. The same DCI size may come from zero-paddingbits in at least a wireless device-specific search space.

In BWP switching, a DCI in the current BWP may need to indicate resourceallocation in the next BWP that the wireless device may be expected toswitch. The resource allocation may be based on the wirelessdevice-specific PRB indexing, which may be per BWP. A range of the PRBindices may change as the BWP changes. The DCI to be transmitted in thecurrent BWP may be based on the PRB indexing for the current BWP. TheDCI may need to indicate the RA in the new BWP, which may cause aresource conflict. To resolve the conflict without significantlyincreasing wireless devices blind detection overhead, the DCI size andbit fields may not change per BWP for a given DCI type.

As the range of the PRB indices may change as the BWP changes, one ormore employed bits among the total bit field for RA may be dependent onthe employed BWP. A wireless device may use the indicated BWP ID thatthe resource allocation may be intended to identify the resourceallocation bit field.

The DCI size of the BWP may be based on a normal DCI detection withoutBWP retuning and/or on a DCI detection during the BWP retuning. A DCIformat may be independent of the BW of the active DL/UL BWP, which maybe called as fallback DCI. At least one of DCI format for DL may beconfigured to have the same size for a wireless device for one or moreconfigured DL BWPs of a serving cell. At least one of the DCI formatsfor UL may be configured to have the same size for a wireless device forone or more configured UL BWPs of a serving cell. A BWP-dependent DCIformat may be monitored at the same time (e.g. a normal DCI) for bothactive DL BWP and active UL BWP. A wireless device may monitor both DCIformats at the same time. A base station may assign the fallback DCIformat to avoid ambiguity during a transition period in the BWPactivation and/or deactivation.

If a wireless device is configured with multiple DL or UL BWPs in aserving cell, an inactive DL and/or UL BWP may be activated by a DCIscheduling a DL assignment or UL grant in the BWP. As the wirelessdevice may be monitoring the PDCCH on the currently active DL BWP, theDCI may comprise an indication to a target BWP that the wireless devicemay switch to for PDSCH reception or UL transmission. A BWP indicationmay be inserted in the wireless device-specific DCI format. The bitwidth of this field may depend on the maximum possible and/or presentlyconfigured number of DL and/or UL BWPs. The BWP indication field may bea fixed size based on the maximum number of configured BWPs.

A DCI format size may match the BW of the BWP in which the PDCCH may bereceived. To avoid an increase in the number of blind decodes, thewireless device may identify the RA field based on the scheduled BWP.For a transition from a small BWP to a larger BWP, the wireless devicemay identify the RA field as being the LSBs of the required RA field forscheduling the larger BWP.

The same DCI size for scheduling different BWPs may be defied by keepingthe same size of resource allocation fields for one or more configuredBWPs. A base station may be aware of a wireless device switching BWPsbased on a reception of ACK/NACK from the wireless device. The basestation may not be aware of a wireless device switching BWPs, forexample, if the base station does not receive at least one response fromthe wireless device. To avoid such a mismatch between base station andwireless device, a fallback mechanism may be used. The base station maytransmit the scheduling DCI for previous BWPs and for newly activatedBWP since the wireless device may receive the DCI on either BWP, forexample, if there is no response from the wireless device. The basestation may confirm the completion of the active BWP switching, forexample, after or in response to the base station receiving a responsefrom the wireless device. The base station may not transmit multipleDCIs, for example, if the same DCI size for scheduling different BWPsmay be considered and CORESET configuration may be the same fordifferent BWPs. DCI format(s) may be configured user-specifically percell rather than per BWP. The wireless device may start to monitorpre-configured search-space on the CORESET, for example, if a wirelessdevice synchronizes to a new BWP.

The size of DCI format in different BWPs may vary and may change atleast due to different size of RA bitmap on different BWPs. The size ofDCI format configured in a cell for a wireless device may be dependenton scheduled BWPs. If the DCI formats may be configured per cell, thecorresponding header size in DCI may be relatively small.

The monitored DCI format size on a search-space of a CORESET may beconfigurable with sufficiently fine granularity and/or the granularitymay be predefined. The monitored DCI format size with sufficientgranularity may be beneficial, for example, if a base station may freelyset the monitoring DCI format size on the search-spaces of a CORESET.The DCI format size may be set such that it may accommodate the largestactual DCI format size variant among one or more BWPs configured in aserving cell.

For a wireless device-specific serving cell, one or more DL BWPs and oneor more UL BWPs may be configured by a dedicated RRC for a wirelessdevice. This may be done as part of the RRC connection establishmentprocedure for a PCell. For an SCell, this may be done via RRCconfiguration indicating the SCell parameters.

A default DL and/or a default UL BWP may be activated since there may beat least one DL and/or UL BWP that may be monitored by the wirelessdevice depending on the properties of the SCell (DL only, UL only, orboth), for example, if a wireless device receives an SCell activationcommand. The BWP may be activated upon receiving an SCell activationcommand. The BWP may be informed to the wireless device via the RRCconfiguration that configured the BWP on this serving cell. For anSCell, RRC signaling for SCell configuration/reconfiguration may be usedto indicate which DL BWP and/or UL BWP may be activated if the SCellactivation command is received by the wireless device. The indicated BWPmay be the initially active DL and/or UL BWP on the SCell. The SCellactivation command may activate DL and/or UL BWP.

For an SCell, RRC signaling for the SCell configuration/reconfigurationmay be used for indicating a default DL BWP on the SCell. The default DLBWP may be used for fallback purposes. The default DL BWP may be same ordifferent from the initially activated DL and/or UL BWP indicated towireless device as part of the SCell configuration. A default UL BWP maybe configured to a wireless device for transmitting PUCCH for SR, forexample, if the PUCCH resources are not configured in every BWP for SR.

An SCell may be for DL only. For a DL only SCell, a wireless device maykeep monitoring an initial DL BWP (e.g., initial active or default)until the wireless device receives SCell deactivation command. An SCellmay be for UL only. For the UL only SCell, the wireless device maytransmit on the indicated UL BWP, for example, if a wireless devicereceives a grant. The wireless device may not maintain an active UL BWPif wireless device does not receive a grant. A failure to maintain theactive UL BWP due to a grant not being received may not deactivate theSCell. An SCell may be for UL and DL. For a UL and DL SCell, a wirelessdevice may keep monitoring an initial DL BWP (e.g., initial active ordefault) until the wireless device receives an SCell deactivationcommand. The UL BWP may be used if there may be a relevant grant or anSR transmission.

A BWP deactivation may not result in a SCell deactivation. The active DLand/or UL BWPs may be considered deactivated, for example, if thewireless device receives the SCell deactivation command.

A wireless device may be expected to perform RACH procedure on an SCellduring activation. Activation of UL BWP may be needed for the RACHprocedure. At an SCell activation, DL only (only active DL BWP) and/orDL/UL (both DL/UL active BWP) may be configured. A wireless device mayselect default UL BWP based on measurement or the network configureswhich one in its activation.

One or more BWPs may be semi-statically configured via wirelessdevice-specific RRC signaling. If a wireless device maintains RRCconnection with a primary component carrier (CC), the BWP in a secondaryCC may be configured via RRC signaling in the primary CC. One or moreBWPs may be semi-statically configured to a wireless device via RRCsignaling in a PCell. A DCI transmitted in an SCell may indicate a BWPamong the one or more configured BWP and grant detailed resource basedon the indicated BWP. For cross-CC scheduling, a DCI transmitted in aPCell may indicate a BWP among the one or more configured BWPs, andgrants detailed resource based on the indicated BWP.

A DL BWP may be initially activated for configuring CORESET formonitoring the first PDCCH in the SCell, for example, if an SCell may beactivated. The DL BWP may serve as a default DL BWP in the SCell. Forthe wireless device performing initial access via a SS block in PCell,the default DL BWP in an SCell may not be derived from SS block forinitial access. The default DL BWP in an SCell may be configured by RRCsignaling in the PCell.

An indication indicating which DL BWP and/or which UL BWP are active maybe in the RRC signaling for SCell configuration and/or reconfiguration,for example, if an SCell is activated. The RRC signaling for SCellconfiguration/reconfiguration may be used for indicating which DL BWPand/or which UL BWP are initially activated if the SCell may beactivated. An indication indicating which DL BWP and/or which UL BWP areactive may be in the SCell activation signaling, for example, if anSCell is activated. SCell activation signaling may be used forindicating which DL BWP and/or which UL BWP are initially activated ifthe SCell may be activated.

For PCells and SCells, initial default BWPs for DL and UL (e.g., forRMSI reception and PRACH transmission) may be valid until at least oneBWP is configured for the DL and UL via RRC wireless device-specificsignaling respectively. The initial default DL/UL bandwidth parts maybecome invalid and new default DL/UL bandwidth parts may take effect.The SCell configuration may comprise default DL/UL bandwidth parts.

An initial BWP on a PCell may be defined by a master information block(MIB). An initial BWP and default BWP may be separately configurable forthe SCell. An initial BWP may be the widest configured BWP of the SCell.A wireless device may retune to a default BWP that may be the narrowBWP. The SCell may be active and may be ready to be opened if anadditional data burst arrives.

A BWP on SCell may be activated by means of cross-cell scheduling DCI.The cross-cell scheduling may be configured for a wireless device. Thebase station may activate a BWP on the SCell by indicating CIF and BWPIin the scheduling DCI.

A wireless device and/or base station may perform synchronizationtracking within an active DL BWP without a SS block. A trackingreference signal (TRS) and/or the DL BWP configuration may beconfigured. A DL BWP with a SS block or TRS may be configured as areference for synchronization tracking.

SS-block based RRM measurements may be decoupled within the BWPframework. Measurement configurations for each RRM and CSI feedback maybe independently configured from the BWP configurations. CSI and SRSmeasurements/transmissions may be performed within the BWP framework.

For a modulation coding scheme (MCS) assignment of the first one or moreDL data packets after active DL BWP switching, the network may assignrobust MCS to a wireless device for the first one or more DL datapackets based on RRM measurement reporting. For a MCS assignment of thefirst one or more DL data packets after active DL BWP switching, thenetwork may signal to a wireless device by active DL BWP switching DCIto trigger aperiodic CSI measurement/reporting to speed up linkadaptation convergence. For a wireless device, periodic CSI measurementoutside the active BWP in a serving cell may not supported. For awireless device, RRM measurement outside active BWP in a serving cellmay be supported. For a wireless device, RRM measurement outsideconfigured BWPs in a serving cell may be supported. RRM measurements maybe performed on a SSB and/or CSI-RS. The RRM/RLM measurements may beindependent of BWPs.

A wireless device may not be configured with aperiodic CSI reports fornon-active DL BWPs. The CSI measurement may be obtained after the BWopening and the wide-band CQI of the previous BWP may be used asstarting point for the other BWP on the component carrier.

A wireless device may perform CSI measurements on the BWP beforescheduling. Before scheduling on a new BWP, a base station may intend tofind the channel quality on the potential new BWPs before scheduling theuser on that BWP. The wireless device may switch to a different BWP andmeasure channel quality on the BWP and then transmit the CSI report.There may be no scheduling needed.

Resource allocation for data transmission for a wireless device notcapable of supporting the carrier bandwidth may be derived based on atwo-step frequency-domain assignment process. A first step may indicatea bandwidth part, and a second step may indicate one or more physicalresource blocks (PRBs) within the bandwidth part.

One or multiple bandwidth part configurations for each component carriermay be semi-statically signaled to a wireless device. A BWP may comprisea group of contiguous PRBs, wherein one or more reserved resources maybebe configured within the bandwidth part. The bandwidth of a bandwidthpart may be equal to or be smaller than the maximal bandwidth capabilitysupported by a wireless device. The bandwidth of a bandwidth part may beat least as large as the SS block bandwidth. The bandwidth part may ormay not contain the SS block. The configuration of a BWP may comprise atleast one of following properties: Numerology, Frequency location (e.g.center frequency), or Bandwidth (e.g. number of PRBs).

A bandwidth part may be associated with one or more numerologies,wherein the one or more numerologies may comprise sub-carrier spacing,CP type, and/or slot duration indicators. A wireless device may expectat least one DL BWP and at least one UL BWP being active among a set ofconfigured BWPs for a given time. A wireless device may receive/transmitwithin active DL/UL bandwidth part(s) using the associated numerology,for example, at least PDSCH and/or PDCCH for DL and PUCCH and/or PUSCHfor UL, or a combination thereof.

Multiple BWPs with same or different numerologies may be active for awireless device simultaneously. The active multiple bandwidth parts maynot imply that it may be required for wireless device to supportdifferent numerologies at the same instance. The active DL/UL bandwidthpart may not span a frequency range larger than the DL/UL bandwidthcapability of the wireless device in a component carrier.

A wireless network may support single and multiple SS blocktransmissions in wideband CC in the frequency domain. For non-CAwireless device with a smaller BW capability and potentially for CAwireless devices, a wireless network may support a measurement gap forRRM measurement and other purposes (e.g., path loss measurement for ULpower control) using SS blocks. There may be no SS blocks in the activeBWPs. A wireless device may be notified of the presence/parameters ofthe SS block(s) and parameters necessary for RRM measurement via atleast one of following: RMSI, other system information, and/or RRCsignaling

A maximum bandwidth for CORESET for RMSI scheduling and PDSCH carryingRMSI may be equal to or smaller than a DL bandwidth of a wirelessnetwork that one or more wireless devices may support in a frequencyrange. For at least for one RACH preamble format, the bandwidth may beequal to or smaller than a UL bandwidth of a wireless network that oneor more wireless devices may support in a frequency range. Other RACHpreamble formats with larger bandwidth than a certain bandwidth of thewireless network that one or more wireless devices may support.

CORESET for RMSI scheduling and PDSCH for RMSI may be confined withinthe BW of one PBCH. CORESET for RMSI scheduling may be confined withinthe BW of one PBCH and PDSCH for RMSI may not be confined within the BWof one PBCH. CORESET for RMSI scheduling and PDSCH for RMSI may not beconfined within the BW of one PBCH.

There may be one active DL BWP for a given time instant. A configurationof a DL bandwidth part may comprise at least one CORESET. PDSCH andcorresponding PDCCH (PDCCH carrying scheduling assignment for the PDSCH)may be transmitted within the same BWP if PDSCH transmission starts nolater than an arbitrary number (K) symbols after the end of the PDCCHtransmission. PDCCH and PDSCH may be transmitted in different BWPs, forexample, if PDSCH transmission starting more than K symbols after theend of the corresponding PDCCH. The value of K may depend on at leastnumerology or reported wireless device retuning time. For the indicationof active DL/UL bandwidth part(s) to a wireless device, DCI (directlyand/or indirectly), MAC CE, Time pattern (e.g. DRX like) and/orcombinations thereof may be considered.

A wireless network may support switching between partial bands for SRStransmissions in a CC. The RF retuning requirement for partial bandswitching may be considered, for example, if a wireless device is notcapable of simultaneous transmission in partial bands in a CC. Thepartial band may indicate a bandwidth part.

Common PRB indexing may be used at least for DL BWP configuration in RRCconnected state. A reference point may be PRB 0, which may be common toone or more wireless devices sharing a wideband CC from networkperspective, regardless of the wireless devices being NB, CA, or WBwireless devices. An offset from PRB 0 to the lowest PRB of the SS blockaccessed by a wireless device may be configured by high layer signaling,for example, via RMSI and/or wireless device-specific signaling. Acommon PRB indexing may be for maximum number of PRBs for a givennumerology, wherein the common PRB indexing may be for RS generation forwireless device-specific PDSCH and/or may be for UL.

There may be an initial active DL/UL bandwidth part pair for a wirelessdevice until the wireless device is explicitly configured and/orreconfigured with one or more BWPs during or after a RRC connection maybe established. The initial active DL/UL bandwidth part may be confinedwithin the wireless device minimum bandwidth for a given frequency band.A wireless network may support activation and/or deactivation of DL andUL BWP by explicit indication. A MAC CE-based approach may be used forthe activation and/or deactivation of DL and UL BWP. A wireless networkmay support an activation and/or deactivation of DL bandwidth part bymeans of timer for a wireless device to switch its active DL bandwidthpart to a default DL bandwidth part. A default DL bandwidth part may bethe initial active DL bandwidth part defined above. The default DLbandwidth part may be reconfigured by the network.

A measurement or transmission SRS outside of the active BWP for awireless device may constitute a measurement gap. The wireless devicemay not monitor CORESET during the measurement gap.

A SRS transmission in an active UL BWP may use the same numerology asconfigured for the BWP. A wireless network may support wireless devicespecific configured bandwidth based on tree-like SRS bandwidth sets.Parameters used for configuring bandwidth allocation, such as CSRS andBSRS, may be reused in a wireless device specific manner. A wirelessnetwork may support to sound substantially all UL PRBs in a BWP.

Frequency hopping for a PUCCH may occur within an active UL BWP for thewireless device. There may be multiple active BWPs, and the active BWPmay refer to BWP associated with the numerology of PUCCH

For paired spectrum, a base station may configure DL and UL BWPsseparately and independently for a wireless device-specific serving cellfor a wireless device. For active BWP switching using at leastscheduling DCI, a DCI for DL may be used for DL active BWP switching anda DCI for UL may be used for UL active BWP switching. A wireless networkmay support a single DCI switching DL and UL BWP jointly.

For unpaired spectrum, a base station may jointly configure a DL BWP andan UL BWP as a pair. The DL and UL BWPs of a DL/UL BWP pair may sharethe same center frequency but may be of different bandwidths for awireless device-specific serving cell for a wireless device. For activeBWP switching using at least scheduling DCI, a DCI for either DL or ULmay be used for switching from one DL/UL BWP pair to another pair,particularly where both DL and UL are activated to a wireless device inthe corresponding unpaired spectrum. There may not be a restriction onDL BWP and UL BWP pairing. For a wireless device, a configured DL (orUL) BWP may overlap in frequency domain with another configured DL (orUL) BWP in a serving cell.

For a serving cell, a maximal number of DL/UL BWP configurations may befor paired spectrum, for example, 4 DL BWPs and 4 UL BWPs. A maximalnumber of DL/UL BWP configurations may be for unpaired spectrum, forexample, 4 DL/UL BWP pairs. A maximal number of DL/UL BWP configurationsmay be for SUL, for example, 4 UL BWPs.

A wireless network may support a dedicated timer for timer-based activeDL BWP switching to the default DL BWP for paired spectrum. A wirelessdevice may start the timer if it switches its active DL BWP to a DL BWPother than the default DL BWP. A wireless device may restart the timerto the initial value if it successfully decodes a DCI to schedule PDSCHin its active DL BWP. A wireless device may switch its active DL BWP tothe default DL BWP if the timer expires.

A wireless network may support a dedicated timer for timer-based activeDL/UL BWP pair switching to the default DL/UL BWP pair for unpairedspectrum. A wireless device may start the timer, for example, if itswitches its active DL/UL BWP pair to a DL/UL BWP pair other than thedefault DL/UL BWP pair. A wireless device may restart the timer to theinitial value, for example, if it successfully decodes a DCI to schedulePDSCH in its active DL/UL BWP pair. A wireless device may switch itsactive DL/UL BWP pair to the default DL/UL BWP pair, for example, if thetimer expires.

RRC signaling for SCell configuration and/or reconfiguration mayindicate a first active DL BWP and/or a first active UL BWP if the SCellmay be activated. A wireless network may support an SCell activationsignaling that does not contain any information related to the firstactive DL/UL BWP. An active DL BWP and/or UL BWP may be deactivated ifthe SCell may be deactivated. The SCell may be deactivated by an SCelldeactivation timer.

A wireless device may be configured with at least a timer fortimer-based active DL BWP (or DL/UL BWP pair) switching and/or a defaultDL BWP (or a DL/UL BWP pair) that may be used if the timer may beexpired. The default DL BWP may be different from the first active DLBWP. A default DL BWP (or DL/UL BWP pair) may be configured/reconfiguredto a wireless device for a PCell. The default DL BWP may be an initialactive DL BWP if no default DL BWP is configured. In a serving cellwhere PUCCH may be configured, a configured UL BWP may comprise PUCCHresources.

A common search space for at least RACH procedure may be configured inone or more BWPs for a wireless device in a PCell. A common search spacefor group-common PDCCH (e.g. SFI, pre-emption indication, etc.) may beconfigured in one or more BWPs for a wireless device in a serving cell.

A DL and/or UL BWP may be configured to a wireless device by resourceallocation Type 1 with one PRB granularity of starting frequencylocation and one PRB granularity of bandwidth size, wherein thegranularity may not imply that a wireless device may adapt its RFchannel bandwidth accordingly.

A DCI format size itself may not be a part of RRC configurationirrespective of BWP activation and deactivation in a serving cell. TheDCI format size may depend on different operations and/or configurationsof different information fields in the DCI.

An initial active DL BWP may be defined as frequency location andbandwidth of RMSI CORESET and numerology of RMSI. The PDSCH deliveringRMSI may be confined within the initial active DL BWP. A wireless devicemay be configured with PRB bundling size(s) per BWP.

A wireless network may support configuring CSI-RS resource on BWP with atransmission BW equal to or smaller than the BWP. A wireless network maysupport at least the CSI-RS spanning contiguous RBs in the granularityof an arbitrary number (X) RBs, for example, if the CSI-RS BW is smallerthan the BWP. If CSI-RS BW is smaller than the corresponding BWP, it maybe at least larger than X RBs. The value of X may be the same ordifferent for beam management and CSI acquisition. The value of X may ormay not be numerology-dependent.

For frequency division duplex (FDD), a base station may configureseparate sets of BWP configurations for DL and/or UL per componentcarrier. A numerology of DL BWP configuration may be applied to at leastPDCCH, PDSCH, and/or corresponding DMRS. A numerology of UL BWPconfiguration may be applied to at least PUCCH, PUSCH, and/orcorresponding DMRS. For time division duplex (TDD), base station mayconfigure separate sets of BWP configurations for DL and/or UL percomponent carrier. A numerology of DL BWP configuration may be appliedto at least PDCCH, PDSCH, and/or corresponding DMRS. A numerology of ULBWP configuration may be applied to at least PUCCH, PUSCH, and/orcorresponding DMRS. A wireless device may not retune the centerfrequency of channel BW between DL and UL, for example, if differentactive DL and UL BWPs are configured.

One or more scheduling request (SR) configurations may be configured fora BWP of a cell for a wireless device. A wireless device may use SRresources configured by the SR configurations in a BWP to indicate tothe base station the numerology/TTI/service type of a logical channel(LCH) or logical channel group (LCG) that triggered the SR. The maximumnumber of SR configurations may be the maximum number of logicalchannels/logical channel groups.

There may be at most one active DL BWP and at most one active UL BWP ata given time for a serving cell. A BWP of a cell may be configured witha specific numerology and/or TTI. For a logical channel and/or logicalchannel group that triggers a SR transmission while the wireless deviceoperates in one active BWP, the corresponding SR may remain triggeredbased on BWP switching.

The logical channel and/or logical channel group to SR configurationmapping may be configured and/or reconfigured based on switching of theactive BWP. The RRC dedicated signaling may configure and/or reconfigurethe logical channel and/or logical channel group to SR configurationmapping on the new active BWP if the active BWP is switched.

A mapping between a logical channel and/or logical channel group and SRconfiguration may be configured if a BWP is configured. The RRC maypre-configure mapping between logical channels and/or logical channelgroups to SR configurations for the configured BWPs. Based on switchingof the active BWP, a wireless device may use the RRC configured mappingrelationship for the new BWP. A RRC may configure the mapping betweenlogical channel and SR configurations for the BWP. The sr-ProhibitTimerand SR_COUNTER corresponding to a SR configuration may continue and thevalue of the sr-ProhibitTimer and the value of the SR_COUNTER may betheir values before the BWP switching.

A plurality of logical channel/logical channel group to SR configurationmappings may be configured in a serving cell. A logical channel/logicalchannel group may be mapped to at most one SR configuration per BWP. Alogical channel/logical channel group mapped onto multiple SRconfigurations in a serving cell may have one SR configuration active ata time, such as that of the active BWP. A plurality of logicalchannel/logical channel group to SR-configuration mappings may besupported in carrier aggregation (CA). A logical channel/logical channelgroup may be mapped to one (or more) SR configuration(s) in each ofPCell and PUCCH-SCell. A logical channel/logical channel groupconfigured to be mapped to one (or more) SR configuration(s) in each ofboth PCell and PUCCH-SCell may have two active SR configurations (one onPCell and one on PUCCH-SCell) at a time for CA. The SR resource isreceived first may be used.

A base station may configure one SR resource per BWP for the samelogical channel/logical channel group. If a SR for one logicalchannel/logical channel group is pending, a wireless device may transmita SR with the SR configuration in another BWP after BWP switching. Thesr-ProhibitTimer and SR_COUNTER for the SR corresponding to the logicalchannel/logical channel group may continue based on BWP switching. Thewireless device may transmit the SR in another SR configurationcorresponding to the logical channel/logical channel group in anotherBWP after BWP switching if a SR for one logical channel/logical channelgroup may be pending,

If multiple SRs for logical channels/logical channel groups mapped todifferent SR configurations are triggered, the wireless device maytransmit one SR corresponding to the highest priority logicalchannel/logical channel group. The wireless device may transmit multipleSRs with different SR configurations. SRs triggered at the same time(e.g., in the same NR-UNIT) by different logical channels/logicalchannel groups mapped to different SR configurations may be merged intoa single SR corresponding to the SR triggered by the highest prioritylogical channel/logical channel group.

If an SR of a first SR configuration is triggered by a first logicalchannel/logical channel group while an SR procedure triggered by a lowerpriority logical channel/logical channel group may be on-going onanother SR configuration, the later SR may be allowed to trigger anotherSR procedure on its own SR configuration independently of the other SRprocedure. A wireless device may be allowed to send independentlytriggered SRs for logical channels/logical channel groups mapped todifferent SR configurations. A wireless device may be allowed to sendtriggered SRs for LCHs corresponding to different SR configurationsindependently.

The dsr-TransMax may be independently configured per SR configuration.The SR_COUNTER may be maintained for each SR configurationindependently. A common SR_COUNTER may be maintained for all the SRconfigurations per BWP.

PUCCH resources may be configured per BWP. The PUCCH resources in thecurrently active BWP may be used for UCI transmission. PUCCH resourcesmay be configured per BWP. PUCCH resources may be utilized in a BWP notcurrently active for UCI transmission. PUCCH resources may be configuredin a default BWP and BWP switching may be necessary for PUCCHtransmission. A wireless device may be allowed to send SR1 in BWP1 eventhough BWP1 may be no longer active. The network may reconfigure (e.g.,pre-configure) the SR resources so that both SR1 and SR2 may besupported in the active BWP. An anchor BWP may be used for SRconfiguration. In an example, the wireless device may send SR2 as afallback.

A logical channel/logical channel group mapped to a SR configuration inan active BWP may also be mapped to the SR configuration in another BWPto imply same or different information, such as numerology and/or TTIand priority. A MAC entity can be configured with a plurality of SRconfigurations within the same BWP. The plurality of the SRconfigurations may be on the same BWP, on different BWPs, or ondifferent carriers. The numerology of the SR transmission may differfrom the numerology that the logical channel/logical channel group thattriggered the SR may be mapped to.

The PUCCH resources for transmission of the SR may be on different BWPsor different carriers for a LCH mapped to multiple SR configurations.The selection of which configured SR configuration within the active BWPto transmit one SR may be up to wireless device implementation ifmultiple SRs are triggered. A single BWP can support multiple SRconfigurations. Multiple sr-ProhibitTimers (e.g., each for one SRconfiguration) may be running at the same time. A drs-TransMax may beindependently configured per SR configuration. A SR_COUNTER may bemaintained for each SR configuration independently. A single logicalchannel/logical channel group may be mapped to zero or one SRconfigurations. A PUCCH resource configuration may be associated with aUL BWP. One or more logical channels may be mapped to none or one SRconfiguration per BWP in CA.

A BWP may consist of a group of contiguous PRBs in the frequency domain.The parameters for each BWP configuration may include numerology,frequency location, bandwidth size (e.g., in terms of PRBs), CORESET.CORESET may be required for each BWP configuration, such as for a singleactive DL bandwidth part for a given time instant. One or more BWPs maybe configured for each component carrier, for example, if the wirelessdevice is in RRC connected mode.

The configured downlink assignment may be initialized (e.g., if notactive) or re-initialized (e.g., if already active) using PDCCH if a newBWP may be activated. For uplink SPS, the wireless device may have toinitialize and/or re-initialize the configured uplink grant if switchingfrom one BWP to anther BWP. If a new BWP is activated, the configureduplink grant may be initialized (e.g., if not already active) orre-initialized (e.g., if already active) using PDCCH.

For type 1 uplink data transmission without grant, there may be no L1signaling to initialize or re-initialize the configured grant. Thewireless device may not determine that the type 1 configured uplinkgrant may be active if the BWP may be switched, for example, even if thewireless device is already active in the previous BWP. The type 1configured uplink grant may be re-configured using RRC dedicatedsignaling for switching the BWP. The type 1 configured uplink grant maybe re-configured using dedicated RRC signaling if a new BWP isactivated.

If SPS is configured on the resources of a BWP and the BWP issubsequently deactivated, the SPS grants or assignments may notcontinue. All configured downlink assignments and configured uplinkgrants using resources of this BWP may be cleared, for example, if a BWPis deactivated. The MAC entity may clear the configured downlinkassignment or/and uplink grants upon receiving activation and/ordeactivation of BWP.

The units of drx-RetransmissionTimer and drx-ULRetransmissionTimer maybe OFDM symbol corresponding to the numerology of the active BWP. If awireless device is monitoring an active DL BWP for a long time withoutactivity, the wireless device may move to a default BWP in order to savepower. A BWP inactivity timer may be introduced to switch from an activeBWP to the default BWP. Autonomous switching to a DL default BWP mayconsider both DL BWP inactivity timers and/or DRX timers, such as HARQRTT and DRX retransmission timers. A DL BWP inactivity timer may beconfigured per MAC entity. A wireless device may be configured tomonitor PDCCH in a default BWP, for example, if a wireless device uses along DRX cycle.

A power headroom report (PHR) may not be triggered due to the switchingof BWP. The support of multiple numerologies/BWPs may not impact PHRtriggers. A PHR may be triggered upon BWP activation. A prohibit timermay start upon PHR triggering due to BWP switching. A PHR may not betriggered due to BWP switching while the prohibit timer may be running.A PHR may be reported per activated and/or deactivated BWP.

Packet Data Convergence Protocol (PDCP) duplication may be in anactivated state while the wireless device receives the BWP deactivationcommand. The PDCP duplication may not be deactivated, for example, ifthe BWP on which the PDCP duplication is operated on is deactivated. ThePDCP entity may stop sending the data to the deactivated RLC buffer, forexample, even if the PDCP duplication may not be deactivated.

RRC signaling may configure a BWP to be activated, for example, if theSCell is activated. Activation and/or deactivation MAC CE may be used toactivate both the SCell and the configured BWP. A HARQ entity can servedifferent BWP within one carrier.

For a wireless device-specific serving cell, one or more DL BWPs and oneor more UL BWPs may be configured by dedicated RRC for a wirelessdevice. A single scheduling DCI may switch the wireless device's activeBWP from one to another. An active DL BWP may be deactivated by means oftimer for a wireless device to switch its active DL bandwidth part to adefault DL bandwidth part. A narrower BWP may be used for DL controlmonitoring and a wider BWP may be used for scheduled data. Small datamay be allowed in the narrower BWP without triggering BWP switching.

For a wireless device with a RRC connected mode, RRC signaling maysupport to configure one or more BWPs (for both DL BWP and UL BWP) for aserving cell (PCell, PSCell). RRC signaling may support to configurezero or more BWPs, for both DL BWP and UL BWP, for a serving cell SCellhaving at least 1 DL BWP. For a wireless device, the PCell, PSCell, andeach SCell may have a single associated SSB in frequency. A celldefining SS block may be changed by synchronous reconfiguration forPCell/PSCell and SCell release/add for the SCell. For example, a SSblock frequency that needs to be measured by the wireless device may beconfigured as individual measurement object, such as having onemeasurement object corresponds to a single SS block frequency. The celldefining SS block may be considered as the time reference of the servingcell and for RRM serving cell measurements based on SSB irrespective ofwhich BWP may be activated. One or more RRC timers and counters relatedto RLM may not be reset, for example, if the active BWP may be changed.

A SR configuration may comprise a collection of sets of PUCCH resourcesacross different BWPs and cells, wherein per cell, at any given timethere may be at most one usable PUCCH resource per LCH. One singleLTE-like set of SR PUCCH resources may be configured per LCH per BWP andone BWP may be active at a time.

BWP switching and cell activation and/or deactivation may not interferewith the operation of the counter and timer. The wireless device may ormay not stop using configured downlink assignments and/or configureduplink grants using resources of the BWP, for example, if a BWP may bedeactivated. The wireless device may suspend the configured grants ofthe or clear it. The wireless device may not suspend and/or clear theconfigured grants. A new timer (e.g., a BWP inactivity timer) may beused to switch from an active BWP to a default BWP after a certaininactive time. The BWP inactivity timer may be independent from the DRXtimers.

A wireless device may not transmit on UL-SCH on the BWP that may A BWPmay be in active during a period of time, for example, if a BWPinactivity timer is running for the BWP. A base station may send acontrol message to a wireless device to configure a first timer value ofa BWP inactivity timer. The first timer value may determine how long aBWP inactivity timer runs, for example, a period of time that a BWPinactivity timer runs. The BWP inactivity timer may be implemented as acount-down timer from a first timer value down to zero. The BWPinactivity timer may be implemented as a count-up timer from zero up toa first timer value down. The BWP inactivity timer may be implemented asa down-counter from a first timer value down to zero. The BWP inactivitytimer may be implemented as a count-up counter from zero up to a firsttimer value down. A wireless device may restart a BWP inactivity timer(e.g., UL BWP and/or DL BWP inactivity timers) if the wireless devicereceives (and/or decodes) a DCI to schedule PDSCH(s) in its active BWP(e.g., its active UL BWP, its active DL BWP, and/or UL/DL BWP pair).

A wireless device may not transmit on UL-SCH on the BWP that may bedeactivated. The wireless device may not monitor the PDCCH on the BWPthat may be deactivated. The wireless device may not transmit PUCCH onthe BWP that may be deactivated. The wireless device may not transmit onPRACH on the BWP that may be deactivated. The wireless device may notflush HARQ buffers if performing BWP switching.

A wireless device-specific DCI may result in increasing signalingoverhead. Signaling overhead may result, for example, due to a basestation having to coordinate scheduling of a plurality of DCIs forswitching one or more BWPs for a plurality of wireless devices.Coordinating a plurality of DCIs may result in complicated processing atthe base station and/or in a delay to schedule the plurality of DCIs forthe plurality of wireless device. Wireless devices may incurinefficiencies using wireless device-specific DCI. For example, aplurality of wireless devices may have the same first active DL BWPand/or UL BWP, such as if an active DL BWP and/or UL BWP is switchedfrom the same first active DL BWP and/or UL BWP to a second DL BWPand/or UL BWP for the plurality of wireless devices. A wirelessdevice-specific DCI for such switching may require a base station totransmit one or more DCIs to the plurality of wireless devices withduplicated (or almost the same) information, which may be inefficient. Awireless device-specific DCI may increase signaling overhead and/or maydecrease spectral efficiency.

A base station may use a group-common DCI that may decrease signalingoverhead and/or increase spectral efficiency. The base station mayindicate a switching of bandwidth parts for a plurality of wirelessdevices using a single group-common DCI. The group-common DCI may bebased on, for example, an index, wireless device identifiers, or acombination of both. The base station may determine a size of thegroup-common DCI. The base station may measure utilization of resourcesin a cell by a plurality of devices. Based on resource utilization, thebase station may determine whether bandwidth part switching should beperformed by one or more wireless devices to improve resourceutilization. A group-common DCI may be used to indicate activation,deactivation, and/or switching of an active DL/UL BWP (e.g., an activeDL BWP and/or an active UL BWP) and/or a default DL/UL BWP (e.g., adefault DL BWP and/or a default UL BWP) for one or more wirelessdevices. A set of DL/UL BWPs to which a wireless device may tune, move,and/or stay in a cell may not be wireless device-specific. The set ofBWPs may be cell-specific and/or may be at least common for a pluralityof wireless devices. One or more wireless devices may switch a DL BWPand/or an UL BWP within a same set of BWPs in a cell. A base station maysend, to a plurality of wireless devices having a same set of BWPs, oneor more messages indicating via a group-common DCI the activating,deactivating, selecting, and/or switching of a DL BWP and/or an UL BWP.

A base station may send, to a wireless device, at least one messagecomprising configuration parameters for a plurality of bandwidth partsof a cell. The at least one message may comprise one or more RRCmessages. The at least one message may further comprise an indexassociated with the wireless device and/or an identifier associated withthe wireless device. The index may comprise a number and/or a valueassociated with a wireless device. The index may comprise a numberand/or a value that is associated with only the wireless device, suchthat the index may differ from each of a plurality of other indices eachassociated with one of a plurality of other wireless devices. Forexample a first index may be associated with a first wireless device, asecond index may be associated with a second wireless device, and/or ak^(th) index may be associated with a k^(th) wireless device, wherein kmay be any integer greater than 1. The index may comprise a numberand/or a value that is associated with a group of wireless devices, suchthat the index may differ from each of a plurality of other indices eachassociated with one group of a plurality of groups of other wirelessdevices. For example a first index may be associated with a first groupof wireless devices, a second index may be associated with a secondgroup of wireless devices, and/or a k^(th) index may be associated witha k^(th) group of wireless devices, wherein k may be any integer greaterthan 1. The index may comprise any index, including, for example, anyindex referenced herein. The index may comprise an indication of thewireless device and/or an indication of a group of wireless device. Theindex may comprise an indication associated with the wireless deviceand/or an indication associated with a group of wireless devices. Theindex may comprise an identifier of the wireless device. The index maycomprise an identifier associated with the wireless device. Theidentifier associated with the wireless device may comprise a wirelessdevice ID, RNTI, etc., that may comprise a unique identifier of thewireless device. The identifier may comprise any identifier, includingfor example, any identifier referenced herein. The configurationparameters may indicate one or more of: a first subcarrier spacing of afirst bandwidth part, a first cyclic prefix of the first bandwidth part,a first number of first contiguous physical resource blocks of the firstbandwidth part, and/or a first offset of a first physical radio resourceblock of the first contiguous physical radio resource blocks. Theconfiguration parameters may indicate one or more of: a secondsubcarrier spacing of a second bandwidth part, a second cyclic prefix ofthe second bandwidth part, a second number of second contiguous physicalresource blocks of the second bandwidth part, and/or a second offset ofa second physical radio resource block of the second contiguous physicalradio resource blocks. The configuration parameters may comprise a timervalue of a second bandwidth part inactivity timer for the secondbandwidth part. The configuration parameters may further compriseparameters of a configured grant of the first bandwidth part. The atleast one message may comprise an indication of a default bandwidthpart. The at least one message may further comprise a radio networkidentifier (e.g., RNTI).

The base station may send, to the wireless device via a control channelof a first bandwidth part, downlink control information (DCI) comprisinga plurality of bandwidth part identifiers. Additionally oralternatively, the DCI may comprise a bandwidth part identifier and aplurality of indicators. The bandwidth part identifier may comprise afield indicating whether a bandwidth part is an active uplink bandwidthpart, an active downlink bandwidth part, a default uplink bandwidthpart, and/or a default downlink bandwidth part. Additionally oralternatively, the DCI may comprise a plurality of bandwidth partfields, each comprising a wireless device identifier and a bandwidthpart identifier. The plurality of indicators may comprise a plurality ofwireless device identifiers. The at least one message may furthercomprise an indication of a size of the DCI. The size of the DCI may befixed (e.g., predefined) or variable. The DCI may be scrambled by theradio network identifier. The plurality of bandwidth part identifiersmay comprise a first bandwidth part identifier indicating a firstbandwidth part and/or a second bandwidth part identifier indicating asecond bandwidth part. One or more of the first bandwidth partidentifier and/or the second bandwidth part identifier may indicate athird bandwidth part paired with the second bandwidth part.

The wireless device may monitor a downlink control channel for one ormore messages from the base station. The wireless device may receive,from the base station, the at least one message comprising a DCI. Thewireless device may determine (e.g., detect) the at least one messagebased at least on a size of the DCI that may be predefined and/or thatmay be informed by the base station, for example, via one or more radioresource control messages. Based on a determination of the size of theDCI, the wireless device may reduce power consumption and decodingcomplexity for detecting and/or decoding the DCI. The wireless devicemay receive, from the base station, the DCI. The wireless device maydetermine, based on the index, a position of a first bandwidth partidentifier in the DCI and/or a position of a first indicator in the DCI.Additionally or alternatively, the wireless device may determine, basedon the identifier for the wireless device, a first bandwidth part fieldin the DCI. The wireless device may switch from the first bandwidth partto a second bandwidth part indicated by: the first bandwidth partidentifier and/or the first bandwidth part field. Additionally oralternatively, the wireless device may switch, based on the firstindicator, from the first bandwidth part to the second bandwidth partindicated by the bandwidth part identifier. The wireless device mayswitch from the first bandwidth part to the second bandwidth part basedon a determination that the first bandwidth part is different from thesecond bandwidth part. If the first bandwidth part is the same as thesecond bandwidth part, the wireless device may not switch from the firstbandwidth part to the second bandwidth part. The wireless device mayreselect the first bandwidth part based on a determination that thesecond bandwidth part is the same as the first bandwidth part. Thewireless device may stay in the first bandwidth part by ignoring theDCI, for example, based on a determination that the second bandwidthpart is the same as the first bandwidth part. If the first bandwidthpart is different from the second bandwidth part, the wireless devicemay switch from the first bandwidth part to the second bandwidth part.The wireless device may start, based on the timer value and after or inresponse to switching from the first bandwidth part to the secondbandwidth part, the second bandwidth part inactivity timer. The wirelessdevice may switch, after or in response to an expiry of the secondbandwidth part inactivity timer, from the second bandwidth part to thedefault bandwidth part. Switching a bandwidth part by the wirelessdevice may comprise the wireless device deactivating the first bandwidthpart and/or activating the second bandwidth part. The switching maycomprise a default bandwidth part switching from the first bandwidthpart to the second bandwidth part. The switching may comprise an activebandwidth part switching from the first bandwidth part to the secondbandwidth part. After or in response to the switching, the wirelessdevice may clear a configured grant and/or release resources associatedwith the configured grant, for example, if the first bandwidth partcomprises the configured grant.

A group-common DCI may comprise one or more fields indicating one ormore of the following: whether the group-common DCI is for an activationand/or deactivation of a DL BWP, a target active DL BWP (e.g., a newactive DL BWP), a source active DL BWP (e.g., a current active DL BWP),a target default DL BWP (e.g., a new default DL BWP), a source defaultDL BWP (e.g., a current default DL BWP), a DL assignment associated withthe target active BWP, and/or an UL grant associated with the targetactive BWP. Additionally or alternatively, the group-common DCI maycomprise one or more fields indicating one or more of the following:whether the group-common DCI is for an activation and/or deactivation ofan UL BWP, a target active UL BWP (e.g., a new active UL BWP), a sourceactive UL BWP (e.g., a current active UL BWP), a target default UL BWP(e.g., a new default UL BWP), a source default UL BWP (e.g., a currentdefault UL BWP), an UL assignment associated with the target active BWP,and/or an UL grant associated with the target active BWP.

The group-common DCI may be scrambled. The group-common DCI may bescrambled by an RNTI, such that the RNTI may be allocated, assigned,and/or transmitted via one or more wireless device-specific RRCsignaling and/or messages. A base station may transmit, to a wirelessdevice, the one or more wireless device-specific RRC signaling and/ormessages that may comprise the RNTI. The RNTI may be shared by aplurality of wireless devices.

A size of the group-common DCI may be fixed and/or semi-staticallyupdated via one or more RRC signaling and/or messages, which may reduceprocessing complexity for DCI decoding by the wireless device. The oneor more RRC signaling and/or messages may be wireless device-specific. Awireless device may search a group-common DCI from a common search spacein a PDCCH with a plurality of possible sizes (e.g., brute forcesearching), for example, if a size of the group-common DCI is unknown tothe wireless device. Using a group-common DCI with a predetermined size,and/or indicating the size of a group-common DCI to the wireless devicebefore the wireless device is to detect the group-common DCI, may reduceprocessing overhead for detecting and/or decoding the group-common DCIby the wireless device side. For example, the predetermined size mayreduce a size of searching space for the DCI detection in the PDCCH. Thesize of the group-common DCI may be predetermined and/or indicated to awireless device before the wireless device receives the group-commonDCI. The size of the group-common DCI may be configured for a wirelessdevice via L1 signaling (e.g., via a DCI) before the wireless devicestarts to monitor a PDCCH (e.g., a CORESET in a current active DL BWP)for the group-common DCI. The size of the group-common DCI may beupdated via L1 signaling (e.g., via a DCI) before the wireless devicestarts to monitor a PDCCH (e.g., a CORESET in a current active DL BWP)for the group-common DCI. A group-common DCI may comprise one or moredummy fields (e.g., zero padding) to maintain and/or to adjust a size ofa group-common DCI.

A format of the group-common DCI may be fixed and/or semi-staticallyupdated, for example, via one or more RRC signaling and/or messages. Thegroup-common DCI may comprise an indicator and/or identifier (e.g.,which may indicate a size and/or a size adjustment), such that awireless device may identify a format of the group-common DCI based onthe indicator and/or identifier. A group-common DCI may comprise one ormore dummy fields (e.g., zero padding).

A base station may use an index-based group-common DCI. The index-basedgroup-common DCI may be used to indicate an activation, deactivation,and/or switching of an active DL, UL, and/or DL/UL pair BWP, and/or adefault DL, UL, and/or DL/UL pair BWP, for one or more wireless devices.The index-based group-common DCI may comprise one or more fieldsindicating one or more of: a target BWP and/or an indicator, wherein atleast one indicator may be associated with at least one of the one ormore wireless devices and may indicate whether a target BWP is a newactive BWP for the wireless device. The target BWP may be indicated inthe one or more fields as an index of a new active DL BWP, UL BWP,and/or DL/UL pair BWP. One or more indices of DL BWP, UL BWP, and/orDL/UL pair BWPs may be configured via one or more RRC signaling and/ormessages that may be wireless device-specific and/or cell-specific(e.g., via broadcasting system information such as RMSI). The index ofthe new active DL BWP, UL BWP, and/or DL/UL pair BWP may be one of theone or more indices. A wireless device may identify (e.g., based on anindex) an associated indicator from the one or more indicators. A basestation may configure the wireless device with the index via one or moreRRC signaling and/or messages. The index may indicate which indicator isassociated with the wireless device (e.g., a position and/or location ofthe associated indicator among the one or more indicators). For example,if a wireless device is configured with index k, the k^(th) indicator ofthe one or more indicators may be associated with the wireless device.The indicator may indicate whether the target BWP (e.g., indicated inthe one or more fields), is applied to a wireless device associated withthe indicator. The indicator may be one or more bits. For example, onevalue (e.g., a value of 1) in the indicator may indicate that thewireless device switches an active BWP to the target BWP (e.g., selectsand/or reselects the target BWP as an active BWP), and another value(e.g., a value of 0) may indicate that the target BWP is not applied tothe wireless device.

FIG. 15 shows an example of an index-based group common DCI. A wirelessdevice 1501 may receive, from a base station 1502, one or more RRCmessages 1503 comprising at least one of a first RNTI, a first index,and/or one or more BWP identifiers associated with one or more BWPs in acell configured for the wireless device. An active and/or a default DL,UL, and/or DL/UL pair BWP may be one of the one or more BWPs indicatedby the one or more BWP identifiers. The wireless device 1501 mayreceive, from the base station 1502, an index-based group common DCI1504. The index-based group common DCI 1504 may be scrambled, forexample, by the first RNTI. A size of the index-based group common DCI1504 may be fixed and/or indicated via one or more RRC messages. Theindex-based group common DCI 1504 may comprise one or more dummy fields,variables, and/or bits (e.g., zero padding) that may be used by the basestation 1502 to match a size of the index-based group common DCI 1504.The index-based group common DCI 1504 may comprise one of the one ormore identifiers (e.g., BWP identifier 1505) and one or more indicators(e.g., indicators 1506-1 to 1506-k). The wireless device 1501 mayidentify an indicator (e.g., 1506-1 to 1506-k) associated with thewireless device 1501 based on the first index. The wireless device 1501may determine, based on a value of its associated indicator, whether toswitch an active BWP to a target BWP associated with the one of the oneor more identifiers (e.g., BWP identifier 1505).

A first wireless device (e.g., the wireless device 1501) may receive afirst index-based group-common DCI (e.g., the index-based group commonDCI 1504). The first index-based group-common DCI may comprise a fieldindicating a first target BWP (e.g., BWP identifier 1505) and at least afirst indicator (e.g., indicator 1506-1 to 1506-k) associated with thefirst wireless device. The first wireless device may identify the firstindicator (e.g., indicator 1506-1 to 1506-k) based on a first indexconfigured via a wireless device-specific RRC message. Based on a valueof the first indicator, the first wireless device may switch, select,and/or reselect an active BWP to the first target BWP. The firstwireless device may restart a first BWP inactive timer associated withthe active BWP, for example, after or in response to receiving the firstindex-based group-common DCI. The first wireless device may restart thefirst BWP inactive timer associated with the active BWP, for example, ifthe first target BWP is applied to the first wireless device.

The wireless device 1501 may receive, from the base station 1502, one ormore RRC messages comprising one or more parameters for indicating atleast one of following: one or more bandwidth parts (BWPs) for the cell;an indicator indicating one of the one or more BWPs as a default BWP forthe cell; an information element (IE) indicating a group-common downlinkcontrol information (DCI) size and/or format for the cell; an index ofthe wireless device 1501; and/or an RNTI. The wireless device 1501 mayattempt a detection of a PDCCH with a group-common DCI 1504 at leastbased on a size indicated by the IE. The group-common DCI 1504 maycomprise one or more of the following: a BWP identifier associated withone of the one or more BWPs; and/or one or more indicators. The wirelessdevice 1501 may determine whether to switch a BWP to a first BWPassociated the at least one BWP identifier (e.g., 1505 in FIG. 15 ), forexample, based on a first indicator associated with the wireless device1501. A position of the first indicator may be indicated at least basedon the index of the wireless device 1501. The group-common DCI 1504 maybe scrambled by at least the RNTI. The BWP may be one of following: anactive UL BWP; an active DL BWP; an active UL/DL pair BWP; a default ULBWP; a default DL BWP; and/or a default UL/DL pair BWP.

A base station may use a group-common DCI comprising one or more BWPidentifiers. One of the one or more BWP identifiers may be associatedwith a wireless device and may indicate a target BWP (e.g., a newdefault DL, UL, or DL/UL pair BWP, or a new active DL, UL, or DL/UL pairBWP) for the wireless device. One or more indices of DL, UL, and/orDL/UL pair BWPs may be configured via one or more RRC messages that maybe wireless device-specific and/or cell-specific (e.g., via broadcastingsystem information such as RMSI). The one of the one or more BWPidentifiers may be one of the one or more indices of a DL BWP, an ULBWP, and/or DL/UL pair BWPs. The wireless device may determine, based onan index, a BWP identifier (from the one or more BWP identifiers) thatmay be associated with the wireless device. The base station mayconfigure the wireless device with the index via one or more RRCmessages. The index may indicate which BWP identifier is associated withthe wireless device (e.g., a position and/or location of the associatedBWP identifier among the one or more BWP identifiers). For example, if awireless device is configured with index k, the k^(th) BWP identifier ofthe one or more BWP identifiers may be associated with the wirelessdevice. The BWP identifier may be 1, 2, or 3 bits for a cell with 2, 4,or 8 BWP candidates, respectively. In a received group-common DCIcomprising one or more BWP identifiers, a BWP identifier associated withthe wireless device may indicate a current active BWP. The wirelessdevice may reselect the current active BWP as an active BWP (e.g., thewireless device may not to switch a current active BWP). The wirelessdevice may restart a BWP inactive timer, for example, if the currentactive BWP is not a default BWP, and/or the wireless device may reselectthe current active BWP as an active BWP. The wireless device may notstart and/or restart a BWP inactive timer, for example, if the currentactive BWP is not a default BWP. In a received group-common DCIcomprising one or more BWP identifiers, for example, a BWP identifierassociated with the wireless device may indicate a first BWP differentfrom a current active BWP. The wireless device may switch a currentactive BWP to the first BWP. The wireless device may restart a BWPinactive timer, for example, if the first BWP is not a default BWP.

FIG. 16 shows an example of a group common DCI comprising one or more ofa plurality of BWP identifiers. A wireless device 1601 may receive, froma base station 1602, one or more RRC messages 1603 comprising one ormore of: a first RNTI, a first index, and/or one or more identifiersassociated with one or more BWPs configured in a cell. An active and/ora default DL, UL, and/or DL/UL pair BWP may be one of the one or moreBWPs. The wireless device 1601 may receive, from the base station 1602,a group common DCI 1604 comprising one or more BWP identifiers (e.g.,1605-1 to 1605-k). The group common DCI 1604 may be scrambled, forexample, by the first RNTI. A size of the group common DCI 1604 may befixed and/or determined via one or more DCI and/or RRC messages. Thegroup common DCI 1604 may comprise one or more dummy fields, variables,and/or bits (e.g., zero padding) that may be used by the base station1602 to match a size of the group common DCI 1604. The group common DCI1604 may comprise one or more BWP identifiers (e.g., 1605-1 to 1605-k)indicating one or more target active or default (DL, UL, or DL/UL pair)BWPs for one or more wireless devices. The wireless device 1601 mayidentify a BWP identifier (e.g., BWP identifier 1605-1 to 1605-k)associated with the wireless device 1601 based on the first index. Thewireless device 1601 may determine whether to switch an active BWP to atarget BWP associated with an identified BWP identifier corresponding tothe wireless device 1601 in the group common DCI 1604, for example, ifor based on whether a current active BWP is different from the targetBWP.

The wireless device 1601 may receive, from the base station 1602, one ormore RRC messages comprising one or more parameters for indicating atleast one of following: one or more bandwidth parts (BWPs) for the cell;an BWP identifier indicating one of the one or more BWPs as a defaultBWP for the cell; an information element (IE) indicating a group-commondownlink control information (DCI) size and/or format for the cell; anindex of the wireless device 1601; and/or an RNTI. The wireless device1601 may attempt, at least based on a size associated with the IE, adetection of a PDCCH with a group-common DCI 1604. The group-common DCI1604 may comprise one or more BWP identifiers 1605-1 to 16-5-k, whereinthe wireless device 1601 may identify a first BWP identifier from theone or more BWP identifiers at least based on the index of the wirelessdevice 1601. The wireless device 1601 may switch a BWP to a first BWPindicated by the first BWP identifier, for example, if the BWP isdifferent from the first BWP. The group-common DCI 1604 may be scrambledby at least the RNTI. The first BWP identifier may be associated withone of the one or more BWPs. The BWP may be one of following: an activeUL BWP; an active DL BWP; an active UL/DL pair BWP; a default UL BWP; adefault DL BWP; or a default UL/DL pair BWP.

A base station may use a group-common DCI to indicate activation,deactivation, and/or switching of an active DL, UL, and/or DL/UL pairBWP, and/or a default DL, UL, and/or DL/UL pair BWP, for one or morewireless devices. The group-common DCI may comprise at least one fieldindicating a target BWP and one or more wireless device identifiers,wherein one of the one or more wireless device identifiers may beassociated with one of the one or more wireless devices. The target BWPmay be indicated in the at least one field as an index of a new activeDL BWP, UL BWP, and/or DL/UL pair BWP. One or more indices of DL BWP, ULBWP, and/or DL/UL pair BWP may be configured via one or more RRCmessages that may be wireless device-specific and/or cell-specific(e.g., via broadcasting system information such as RMSI). The index maybe one of the one or more indices. A wireless device may determine,based on a presence or an absence of a wireless device identifier,associated with the wireless device, in the group-common DCI, whether ornot the target BWP indicated in the at least one field is applied to thewireless device. The base station may configure the wireless device withthe wireless device identifier via one or more RRC messages. Thewireless device identifier may be a C-RNTI assigned, configured, and/orallocated to the wireless device. The wireless device identifier may beassociated with the C-RNTI (e.g., a truncated C-RNTI). The wirelessdevice identifier may be separately assigned, configured, and/orallocated to the wireless device by the base station via at least onewireless device-specific RRC message. The target BWP may indicate acurrent active BWP, for example, if the wireless device receives agroup-common DCI comprising at least one field indicating a target BWPand/or one or more wireless device identifiers. The wireless device mayreselect the current active BWP as an active BWP (e.g., may not toswitch a current active BWP), for example, if the group-common DCIcomprises a wireless device identifier associated with the wirelessdevice. The wireless device may restart a BWP inactive timer, forexample, if the current active BWP is not a default BWP. The wirelessdevice may not restart a BWP inactive timer, for example, if the currentactive BWP is not a default BWP. The target BWP may indicate a first BWPdifferent from a current active BWP, for example, if the wireless devicereceives a group-common DCI comprising at least one field indicating atarget BWP and/or one or more wireless device identifiers comprising awireless device identifier corresponding to the wireless device. Thewireless device may switch a current active BWP to the first BWP, forexample, if the group-common DCI comprises a wireless device identifierassociated with the wireless device. The wireless device may restart aBWP inactive timer, for example, if the first BWP is not a default BWP.The wireless device may ignore, abandon, and/or discard the group-commonDCI, for example, if the wireless device receives a group-common DCIcomprising at least one field indicating a target BWP and/or one or morewireless device identifiers that are not associated with or indicatingthe wireless device.

FIG. 17 shows an example of a group common DCI comprising a BWPidentifier and one or more wireless device identifiers. A wirelessdevice 1701 may receive, from a base station 1702, one or more RRCmessages 1703 comprising one or more of a first RNTI, a first wirelessdevice identifier, and/or one or more identifiers associated with one ormore BWPs in a cell configured with the wireless device 1701. An activeand/or a default DL, UL, and/or DL/UL pair BWP may be one of the one ormore BWPs. The wireless device 1701 may receive, from the base station1702, a group common DCI 1704. The group common DCI 1704 may bescrambled, for example, by the first RNTI. A size of the group commonDCI 1704 may be fixed and/or determined via one or more DCI and/or RRCmessages. The group common DCI 1704 may comprise one or more dummyfields, variables, and/or bits (e.g., zero padding) that may be used bythe base station 1702 to match a size of the group common DCI 1704. Thegroup common DCI 1704 may comprise at least one field indicating atarget BWP (e.g., BWP identifier 1705) and one or more wireless deviceidentifiers (e.g., 1706-1 to 1706-k). The wireless device 1701 mayswitch, select, and/or reselect an active BWP to the target BWP, forexample, if the one or more wireless device identifiers comprise thefirst wireless device identifier associated with the wireless device1701.

A base station may use a group-common DCI that may comprise a fixed sizeto indicate activation, deactivation, and/or switching of an active DLBWP, UL BWP, and/or DL/UL pair BWP, and/or a default DL BWP, UL BWP,and/or DL/UL pair BWP, for one or more wireless devices. Thegroup-common DCI may comprise at least one BWP field, wherein the atleast one BWP field may comprise at least one field indicating a targetBWP and a wireless device identifier. The wireless device may be one ofthe one or more wireless devices. The target BWP may be indicated in theat least one field as an index of a new active DL BWP, UL BWP, or DL/ULpair BWP. For example, one or more indices of DL BWP, UL BWP, and/orDL/UL pair BWP may be configured with the wireless device by the basestation via one or more RRC messages that may be wirelessdevice-specific and/or cell-specific (e.g., via broadcasting systeminformation such as RMSI). The index may be one of the one or moreindices. A wireless device may determine, based on a presence or anabsence of a wireless device identifier, associated with the wirelessdevice, in the group-common DCI, whether or not the target BWP indicatedin the at least one field is applied to the wireless device. The basestation may configure the wireless device with the wireless deviceidentifier via one or more RRC messages. The wireless device identifiermay be a C-RNTI assigned, configured, and/or allocated to the wirelessdevice. The wireless device identifier may be associated with the C-RNTI(e.g., a truncated C-RNTI. The wireless device identifier may beseparately assigned, configured, and/or allocated to the wireless deviceby the base station via at least one wireless device-specific RRCmessage. The wireless device may attempt to detect at least one BWPfield from the one or more BWP fields based on a wireless deviceidentifier associated with the wireless device, for example, if thewireless device receives a group-common DCI comprising one or more BWPfields. The wireless device may identify the wireless device identifierfrom the group-common DCI, for example, if a size of a BWP field may befixed. The wireless device may ignore, abandon, and/or discard thegroup-common DCI, for example, if the group-common DCI does not comprisethe wireless device identifier. The wireless device may switch an activeBWP to a target BWP (wherein the group-common DCI may comprise at leastone BWP filed comprising the wireless device identifier and the targetBWP), for example, if the group-common DCI comprises the wireless deviceidentifier. The target BWP may indicate a current active BWP. Thewireless device may reselect the current active BWP as an active BWP(e.g., the wireless device may not to switch a current active BWP). Thewireless device may restart a BWP inactive timer, for example, if thecurrent active BWP is not a default BWP. The wireless device may notrestart a BWP inactive timer, for example, if the current active BWP isnot a default BWP. The wireless device may switch the current active BWPto the first target BWP (wherein the group-common DCI may comprise atleast one BWP filed comprising the wireless device identifier and thefirst target BWP), for example, if the group-common DCI comprises thewireless device identifier and a first target BWP is different from acurrent active BWP. The wireless device may restart a BWP inactivetimer, for example, if the first target BWP is not a default BWP.

FIG. 18 shows an example of a group common DCI comprising one or more ofa plurality of BWP fields. A wireless device 1801 may receive, from abase station 1802, one or more RRC messages 1803 comprising one or moreof: a first RNTI, a first wireless device identifier, and/or one or moreidentifiers associated with one or more BWPs configured in a cell. Anactive and/or a default DL, UL, and/or DL/UL pair BWP may be one of theone or more BWPs. The wireless device 1801 may receive, from the basestation 1802, a group common DCI 1804. The group common DCI 1804 may bescrambled, for example, by the first RNTI. A size of the group commonDCI may be fixed and/or determined based on a size indicator transmittedvia one or more DCI and/or RRC messages. The group common DCI 1804 maycomprise one or more dummy fields, variables, and/or bits (e.g., zeropadding 1807) that may be used by a base station to match a size of thegroup common DCI 1804. The group common DCI 1804 may comprise at leastone BWP field (e.g., 1805 and/or 1806) that may comprise a wirelessdevice identifier (e.g., 1805-a) and a BWP identifier (e.g., 1805-b)that may indicate one of the one or more BWPs configured for a firstwireless device (e.g., the wireless device 1801) associated with thewireless device identifier (e.g., 1805-a). A BWP identifier may comprisem-bits. The BWP identifier 1805-b may be unique to the wireless deviceassociated with the wireless device identifier 1805-a. Each BWP field(e.g., 1805 and 1806) may comprise a wireless device identifier and aBWP identifier that is unique to a wireless device. The wireless device1801 may switch, select, and/or reselect an active BWP to the target BWPindicated by the BWP identifier, for example, if the first wirelessdevice associated with the wireless device identifier is matched with,corresponds to, and/or is the same as the wireless device.

The wireless device 1801 may receive, from the base station 1802, one ormore RRC messages comprising grant-free configuration parameters forindicating at least one of following: one or more bandwidth parts(BWPs); an indicator indicating one of the one or more BWPs as a defaultBWP; an information element (IE) indicating a group-common downlinkcontrol information (DCI) size and/or format; a first identifier of thewireless device 1801; and/or an RNTI. The wireless device 1801 mayattempt a detection of a PDCCH with a group-common DCI at least based ona size associated with the one of the at least one IE. The group-commonDCI 1804 may comprise at least one BWP identifier (e.g., 1805-b)associated with one of the one or more BWPs. The wireless device 1801may determine, based on a presence or an absence of the first identifierin the group-common DC 18041, whether to switch a BWP to a first BWPassociated with the at least one BWP identifier. The group-common DCImay be scrambled by at least the RNTI. The BWP may be one or more offollowing: an active UL BWP; an active DL BWP; an active UL/DL pair BWP;a default UL BWP; a default DL BWP; and/or a default UL/DL pair BWP.

FIG. 19 shows an example for a group common control message. One or morefirst messages may be sent for configuration of one or more BWPs for oneor more wireless devices. One or more second messages may be sent forswitching to an active BWP indicated by a group common control message.A base station 1902 may send, to one or more wireless devices 1901-1,1901-n, to 1901-k, where n is any integer greater than 1, and k is anyinteger greater than or equal to n, one or more control messages. Thebase station 1902 may send one or more first RRC messages 1903-1 to thewireless device 1901-1. The base station 1902 may send one or moresecond RRC messages 1903-n to the wireless device 1901-n. The basestation 1902 may send one or more third RRC messages 1903-k to thewireless device 1901-k. The one or more first RRC messages 1901-1, theone or more second RRC messages 1901-n, and the one or more third RRCmessages 1901-k may comprise parameters for indicating a radio networktemporary identifier used for detecting and/or decoding a group commoncontrol message 1904. The one or more first RRC messages 1901-1, the oneor more second RRC messages 1901-n, and the one or more third RRCmessages 1901-k may comprise parameters for configuring one or more BWPsfor each of a respective k wireless devices. Each of a the respective kwireless devices may have the same or different BWP configurations. Thebase station 1902 may send, to the one or more wireless devices 1901-1,1901-n, and/or 1901-k, a group common control message 1904. The groupcommon control message 1904 may be scrambled by the radio networktemporary identifier. The group common control message 1904 may comprisean indication for switching of an active BWP for the one or morewireless devices 1901-1, 1901-n, and/or 1901-k. Based on the indicationfor switching of an active BWP, the one or more wireless devices 1901-1,1901-n, and/or 1901-k may switch an active BWP to a BWP indicated by thegroup common control message 1904. The BWP may be indicated in one ormore ways. For example, the group common control message 1904 maycomprise a BWP identifier of an active BWP that may be applied to one ormore wireless devices among k wireless devices. The group common controlmessage 1904 may comprise one or more BWP identifiers corresponding toone or more active BWPs, each of the one or more BWP identifiers may beassociated with one of k wireless devices. A wireless device mayidentify a BWP identifier corresponding to the wireless device based ona position indicator configured with the wireless device. A wirelessdevice may identify a BWP identifier corresponding the wireless devicebased on a wireless device identifier configured with the wirelessdevice. The one or more wireless devices 1901-1, 1901-n, and/or 1901-kmay switch an active BWP, for example, only if the BWP indicated in thegroup common control message 1904 is different from a current active BWPfor the respective wireless device of the one or more wireless devices1901-1, 1901-n, and/or 1901-k.

FIG. 20 shows an example of a group common control procedure for BWPswitching that may be performed by a base station. At step 2001, a basestation may determine one or more BWPs for one or more of k wirelessdevices, where k may be any positive integer corresponding to a numberof wireless devices in a cell served by the base station. The basestation may send, to the one or more of k wireless devices, one or moreradio control messages comprising configuration parameters for one ormore BWPs for any number of the k wireless devices. At step 2002, thebase station may determine to switch an active BWP for any number of thek wireless devices. This determination may be based on, for example,radio conditions in the cell or in neighboring cells. If a determinationis not made to switch an active BWP, step 2002 may be repeated, forexample, after a duration of time or upon the base station receiving anindication to switch an active BWP. If a determination is made to switchan active BWP, the process may continue to step 2003. At step 2003, thebase station may determine one or more new BWPs to be activated for anyof the k wireless devices. This determination may be based on, forexample, radio resource usages of the k wireless devices. At step 2004,the base station may determine a group common control message indicatinga BWP switching of an active BWP for one or more of the k wirelessdevices. The base station may send the group common control message toone or more of the k wireless devices.

FIG. 21 shows an example of a group common control procedure for BWPswitching that may be performed by a wireless device. At step 2101, awireless device may receive, from a base station, one or more radiocontrol messages comprising configuration parameters for one or moreBWPs. The wireless device may determine, based on the one or more radiocontrol messages, an active BWP from one or more BWPs. At step 2102, thewireless device may determine whether a group common control message hasbeen received. This determination may be based on an identifier in DCI.If a determination is made that a group common control message has notbeen received, step 2102 may be repeated, for example, after a durationof time or upon the wireless device receiving an indication of a groupcommon control message. If a determination is made that a group commoncontrol message has been received, the process may continue to step2103. At step 2103, the wireless device may determine whether to switchan active BWP. This determination may be based on whether an indicationof a BWP in the group common control message is different from theactive BWP for the wireless device. If a determination is made not toswitch an active BWP, the process may return to step 2102. If adetermination is made to switch an active BWP, the wireless device mayproceed to step 2104. At step 2104, the wireless device may switch anactive BWP to a new BWP from a current BWP. After the wireless deviceswitches an active BWP, the process may repeat or end.

FIG. 22 shows general hardware elements that may be used to implementany of the various computing devices discussed herein, including, forexample, the base station 401, the wireless device 406, or any otherbase station, wireless device, or computing device described herein. Thecomputing device 2200 may include one or more processors 2201, which mayexecute instructions stored in the random access memory (RAM) 2203, theremovable media 2204 (such as a Universal Serial Bus (USB) drive,compact disk (CD) or digital versatile disk (DVD), or floppy diskdrive), or any other desired storage medium. Instructions may also bestored in an attached (or internal) hard drive 2205. The computingdevice 2200 may also include a security processor (not shown), which mayexecute instructions of one or more computer programs to monitor theprocesses executing on the processor 2201 and any process that requestsaccess to any hardware and/or software components of the computingdevice 2200 (e.g., ROM 2202, RAM 2203, the removable media 2204, thehard drive 2205, the device controller 2207, a network interface 2209, aGPS 2211, a Bluetooth interface 2212, a WiFi interface 2213, etc.). Thecomputing device 2200 may include one or more output devices, such asthe display 2206 (e.g., a screen, a display device, a monitor, atelevision, etc.), and may include one or more output device controllers2207, such as a video processor. There may also be one or more userinput devices 2208, such as a remote control, keyboard, mouse, touchscreen, microphone, etc. The computing device 2200 may also include oneor more network interfaces, such as a network interface 2209, which maybe a wired interface, a wireless interface, or a combination of the two.The network interface 2209 may provide an interface for the computingdevice 2200 to communicate with a network 2210 (e.g., a RAN, or anyother network). The network interface 2209 may include a modem (e.g., acable modem), and the external network 2210 may include communicationlinks, an external network, an in-home network, a provider's wireless,coaxial, fiber, or hybrid fiber/coaxial distribution system (e.g., aDOCSIS network), or any other desired network. Additionally, thecomputing device 2200 may include a location-detecting device, such as aglobal positioning system (GPS) microprocessor 2211, which may beconfigured to receive and process global positioning signals anddetermine, with possible assistance from an external server and antenna,a geographic position of the computing device 2200.

The example in FIG. 22 is a hardware configuration, although thecomponents shown may be implemented as software as well. Modificationsmay be made to add, remove, combine, divide, etc. components of thecomputing device 2200 as desired. Additionally, the components may beimplemented using basic computing devices and components, and the samecomponents (e.g., processor 2201, ROM storage 2202, display 2206, etc.)may be used to implement any of the other computing devices andcomponents described herein. For example, the various componentsdescribed herein may be implemented using computing devices havingcomponents such as a processor executing computer-executableinstructions stored on a computer-readable medium, as shown in FIG. 22 .Some or all of the entities described herein may be software based, andmay co-exist in a common physical platform (e.g., a requesting entitymay be a separate software process and program from a dependent entity,both of which may be executed as software on a common computing device).

One or more features of the disclosure may be implemented in acomputer-usable data and/or computer-executable instructions, such as inone or more program modules, executed by one or more computers or otherdevices. Generally, program modules include routines, programs, objects,components, data structures, etc. that perform particular tasks orimplement particular abstract data types when executed by a processor ina computer or other data processing device. The computer executableinstructions may be stored on one or more computer readable media suchas a hard disk, optical disk, removable storage media, solid statememory, RAM, etc. The functionality of the program modules may becombined or distributed as desired. The functionality may be implementedin whole or in part in firmware or hardware equivalents such asintegrated circuits, field programmable gate arrays (FPGA), and thelike. Particular data structures may be used to more effectivelyimplement one or more features of the disclosure, and such datastructures are contemplated within the scope of computer executableinstructions and computer-usable data described herein.

Many of the elements in examples may be implemented as modules. A modulemay be an isolatable element that performs a defined function and has adefined interface to other elements. The modules may be implemented inhardware, software in combination with hardware, firmware, wetware(i.e., hardware with a biological element) or a combination thereof, allof which may be behaviorally equivalent. For example, modules may beimplemented as a software routine written in a computer languageconfigured to be executed by a hardware machine (such as C, C++,Fortran, Java, Basic, Matlab or the like) or a modeling/simulationprogram such as Simulink, Stateflow, GNU Octave, or LabVIEWMathScript.Additionally or alternatively, it may be possible to implement modulesusing physical hardware that incorporates discrete or programmableanalog, digital and/or quantum hardware. Examples of programmablehardware may comprise: computers, microcontrollers, microprocessors,application-specific integrated circuits (ASICs); field programmablegate arrays (FPGAs); and complex programmable logic devices (CPLDs).Computers, microcontrollers, and microprocessors may be programmed usinglanguages such as assembly, C, C++ or the like. FPGAs, ASICs, and CPLDsmay be programmed using hardware description languages (HDL), such asVHSIC hardware description language (VHDL) or Verilog, which mayconfigure connections between internal hardware modules with lesserfunctionality on a programmable device. The above mentioned technologiesmay be used in combination to achieve the result of a functional module.

A non-transitory tangible computer readable media may compriseinstructions executable by one or more processors configured to causeoperations of multi-carrier communications described herein. An articleof manufacture may comprise a non-transitory tangible computer readablemachine-accessible medium having instructions encoded thereon forenabling programmable hardware to cause a device (e.g., a wirelessdevice, wireless communicator, a UE, a base station, and the like) toenable operation of multi-carrier communications described herein. Thedevice, or one or more devices such as in a system, may include one ormore processors, memory, interfaces, and/or the like. Other examples maycomprise communication networks comprising devices such as basestations, wireless devices or user equipment (UE), servers, switches,antennas, and/or the like. A network may comprise any wirelesstechnology, including but not limited to, cellular, wireless, WiFi, 4G,5G, any generation of 3GPP or other cellular standard or recommendation,wireless local area networks, wireless personal area networks, wirelessad hoc networks, wireless metropolitan area networks, wireless wide areanetworks, global area networks, space networks, and any other networkusing wireless communications. Any device (e.g., a wireless device, abase station, or any other device) or combination of devices may be usedto perform any combination of one or more of steps described herein,including, for example, any complementary step or steps of one or moreof the above steps.

Although examples are described above, features and/or steps of thoseexamples may be combined, divided, omitted, rearranged, revised, and/oraugmented in any desired manner. Various alterations, modifications, andimprovements will readily occur to those skilled in the art. Suchalterations, modifications, and improvements are intended to be part ofthis description, though not expressly stated herein, and are intendedto be within the spirit and scope of the disclosure. Accordingly, theforegoing description is by way of example only, and is not limiting.

1. A method comprising: receiving, by a wireless device from a base station, one or more messages comprising an indication of a field, among a plurality of fields in downlink control information (DCI), that the wireless device should use for bandwidth part switching; receiving, via a control channel of a first bandwidth part, the DCI comprising the plurality of fields, wherein each field of the plurality of fields indicates a bandwidth part for a different wireless device; and switching from the first bandwidth part to a second bandwidth part indicated by the field.
 2. The method of claim 1, wherein the switching comprises deactivating the first bandwidth part.
 3. The method of claim 1, wherein the switching comprises activating the second bandwidth part.
 4. The method of claim 1, wherein the switching comprises reselecting the first bandwidth part based on a determination that the second bandwidth part is the same as the first bandwidth part.
 5. The method of claim 1, wherein the one or more messages further comprise a timer value for a second bandwidth part inactivity timer associated with the second bandwidth part, and wherein the method further comprises: starting, based on the timer value and based on the switching, the second bandwidth part inactivity timer.
 6. The method of claim 5, wherein the one or more messages further comprises an indication of a default bandwidth part, and wherein the method further comprises: switching, based on an expiry of the second bandwidth part inactivity timer, from the second bandwidth part to the default bandwidth part.
 7. The method of claim 1, wherein the one or more messages further comprises an indication a configured grant of the first bandwidth part, and wherein the method further comprises clearing the configured grant after the switching.
 8. The method of claim 1, wherein the one or more messages further comprises a radio network identifier.
 9. The method of claim 8, wherein the DCI is scrambled by the radio network identifier.
 10. The method of claim 1, wherein the indication of the field comprises an index associated with the wireless device, wherein the method further comprises determining, based on the index, a position of the field in the DCI.
 11. The method of claim 10, wherein the index differs from each of a plurality of other indices each associated with one of a plurality of other wireless devices.
 12. The method of claim 1, wherein the indication of the field comprises a wireless device-specific identifier associated with the wireless device, wherein the method further comprises determining, based on a wireless device identifier in the DCI indicating the wireless device-specific identifier, the field.
 13. A wireless device comprising: one or more processors; and memory storing instructions that, when executed by the one or more processors, cause the wireless device to: receive, from a base station, one or more messages comprising an indication of a field, among a plurality of fields in downlink control information (DCI), that the wireless device should use for bandwidth part switching; receive, via a control channel of a first bandwidth part, the DCI comprising the plurality of fields, wherein each field of the plurality of fields indicates a bandwidth part for a different wireless device; and switch from the first bandwidth part to a second bandwidth part indicated by the field.
 14. The wireless device of claim 13, wherein the instructions, when executed by the one or more processors, cause the wireless device to deactivate, based on switching from the first bandwidth part to the second bandwidth part, the first bandwidth part.
 15. The wireless device of claim 13, wherein the instructions, when executed by the one or more processors, cause the wireless device to activate, prior to switching from the first bandwidth part to the second bandwidth part, the second bandwidth part.
 16. The wireless device of claim 13, wherein the instructions, when executed by the one or more processors, cause the wireless device to reselect the first bandwidth part based on a determination that the second bandwidth part is the same as the first bandwidth part.
 17. The wireless device of claim 13, wherein the one or more messages further comprise a timer value for a second bandwidth part inactivity timer associated with the second bandwidth part, and wherein the instructions, when executed by the one or more processors, cause the wireless device to: start, based on the timer value and based on switching from the first bandwidth part to the second bandwidth part, the second bandwidth part inactivity timer.
 18. The wireless device of claim 17, wherein the one or more messages further comprises an indication of a default bandwidth part, and wherein the instructions, when executed by the one or more processors, cause the wireless device to: switch, based on an expiry of the second bandwidth part inactivity timer, from the second bandwidth part to the default bandwidth part.
 19. The wireless device of claim 13, wherein the one or more messages further comprises an indication a configured grant of the first bandwidth part, and wherein the instructions, when executed by the one or more processors, cause the wireless device to clear the configured grant after switching from the first bandwidth part to the second bandwidth.
 20. The wireless device of claim 13, wherein the one or more messages further comprises a radio network identifier.
 21. The wireless device of claim 20, wherein the instructions, when executed by the one or more processors, cause the wireless device to descramble the DCI using the radio network identifier.
 22. The wireless device of claim 13, wherein the indication of the field comprises an index associated with the wireless device, wherein the instructions, when executed by the one or more processors, cause the wireless device to determine, based on the index, a position of the field in the DCI.
 23. The wireless device of claim 22, wherein the index differs from each of a plurality of other indices each associated with one of a plurality of other wireless devices.
 24. The wireless device of claim 13, wherein the indication of the field comprises a wireless device-specific identifier associated with the wireless device, wherein the instructions, when executed by the one or more processors, cause the wireless device to determine, based on a wireless device identifier in the DCI indicating the wireless device-specific identifier, the field.
 25. A non-transitory computer-readable medium comprising instructions that, when executed, configure a wireless device to: receive, from a base station, one or more messages comprising an indication of a field, among a plurality of fields in downlink control information (DCI), that the wireless device should use for bandwidth part switching; receive, via a control channel of a first bandwidth part, the DCI comprising the plurality of fields, wherein each field of the plurality of fields indicates a bandwidth part for a different wireless device; and switch from the first bandwidth part to a second bandwidth part indicated by the field.
 26. The non-transitory computer-readable medium of claim 25, wherein the instructions, when executed, configure the wireless device to deactivate, based on switching from the first bandwidth part to the second bandwidth part, the first bandwidth part.
 27. The non-transitory computer-readable medium of claim 25, wherein the instructions, when executed, configure the wireless device to activate, prior to switching from the first bandwidth part to the second bandwidth part, the second bandwidth part.
 28. The non-transitory computer-readable medium of claim 25, wherein the instructions, when executed, configure the wireless device to reselect the first bandwidth part based on a determination that the second bandwidth part is the same as the first bandwidth part.
 29. The non-transitory computer-readable medium of claim 25, wherein the one or more messages further comprise a timer value for a second bandwidth part inactivity timer associated with the second bandwidth part, and wherein the instructions, when executed, configure the wireless device to: start, based on the timer value and based on switching from the first bandwidth part to the second bandwidth part, the second bandwidth part inactivity timer.
 30. The non-transitory computer-readable medium of claim 29, wherein the one or more messages further comprises an indication of a default bandwidth part, and wherein the instructions, when executed, configure the wireless device to: switch, based on an expiry of the second bandwidth part inactivity timer, from the second bandwidth part to the default bandwidth part.
 31. The non-transitory computer-readable medium of claim 25, wherein the one or more messages further comprises an indication a configured grant of the first bandwidth part, and wherein the instructions, when executed, configure the wireless device to clear the configured grant after switching from the first bandwidth part to the second bandwidth.
 32. The non-transitory computer-readable medium of claim 25, wherein the one or more messages further comprises a radio network identifier.
 33. The non-transitory computer-readable medium of claim 32, wherein the instructions, when executed, configure the wireless device to descramble the DCI using the radio network identifier.
 34. The non-transitory computer-readable medium of claim 25, wherein the indication of the field comprises an index associated with the wireless device, wherein the instructions, when executed, configure the wireless device to determine, based on the index, a position of the field in the DCI.
 35. The non-transitory computer-readable medium of claim 34, wherein the index differs from each of a plurality of other indices each associated with one of a plurality of other wireless devices.
 36. The non-transitory computer-readable medium of claim 25, wherein the indication of the field comprises a wireless device-specific identifier associated with the wireless device, wherein the instructions, when executed, configure the wireless device to determine, based on a wireless device identifier in the DCI indicating the wireless device-specific identifier, the field. 